Issue with ISC Early Access Trigger: "Source Account Created" Event Not Retrieving Identity for Workflow Processing

Issue Summary:
We have enabled the ISC early access event triggers, specifically for the “Source Account Created” event, which occurs after a new account is detected during an account aggregation and refresh from a source. In our workflow, we aim to trigger on the source account creation event and subsequently write back the ADEmail for the detected identity to a different source.

Problem:
After the source account trigger executes, we are not receiving the associated identity for processing. We need assistance in ensuring that the detected identity, tied to the source account creation, is available for processing within the workflow.

Details:
We have verified that the source account trigger is firing as expected.
The issue arises when attempting to capture the identity for further processing after the event is triggered.
This is impacting our ability to perform the necessary writeback operation to another source.
We would appreciate guidance or a solution to ensure the identity associated with the newly created source account is retrievable and available for processing within our workflow.

See workflow execution results below:

ActivityTaskScheduled	2024-09-16T21:56:56.995384123Z	{"displayName":"Get Identity","input":{"id.$":"$.trigger.identity.id","method":"GET","path":"v3/identities/<no value>","service":"mice"},"stepName":"getIdentity","task":"sp:get-identity"}
ActivityTaskStarted	2024-09-16T21:56:56.995418595Z	{"attempts":1,"displayName":"Get Identity","stepName":"getIdentity","task":"sp:get-identity"}
ActivityTaskFailed	2024-09-16T21:56:57.158646027Z	{"displayName":"Get Identity","error":"request failed: 404 - 404 Not Found: ","stepName":"getIdentity","task":"sp:get-identity"}
WorkflowExecutionFailed	2024-09-16T21:56:57.180497221Z	{"error":"task failed: activity error (type: sp:internal:http, scheduledEventID: 5, startedEventID: 6, identity: 1@sp-workflow-engine-stg-us-east-1-74db679f5f-fvxlc@): request failed: 404 -

Here’s an image of what we currently have configured:

Could you try using just Get Identity directly without any loop Instead of Get List of Identities and $.trigger.identityId as the input.

1 Like

This is what I had to do, you do get the identity ID in the trigger, so I added a step to retrieve the full identity and use the data in the following steps.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.