Delay in Workflow Execution ID Availability when using External Trigger

SailPoint Human Fabric (SHF) SHF Discussion and Questions
, ,
1

We have implemented a SailPoint ISC workflow integration where the workflow is triggered externally using external trigger API endpoint.

External Trigger response returns as workflow-execution-id.

We then use this workflow-execution-id to track the workflow execution status via: https://tenant.api.identitynow.com/v2024/workflow-executions/

This pattern has been working fine.

Recently, we have started noticing a delay between the Workflow being triggered and the workflow-execution-id being returned, and the Workflow execution ID becoming available in the ISC UI/API.

  • The workflow execution ID is returned immediately in the external trigger API response.
  • However, the same workflow execution ID is not available for status tracking for up to ~5 mins in both UI and via API.
  • Once it becomes available, the workflow shows the total execution time of under ~5 seconds.

This workflow behavior is impacting our use case as we rely on near real-time workflow execution (within a few seconds). We already have wait and retry logic to check workflow completion. The current issue is different as the workflow execution ID is not resolvable initially so the request to the workflow-executions endpoint fails.

Has anyone observed delays in workflow execution ID visibility after triggering via the external request trigger? Any recent changes in how workflows are processed. We wanted to know if this is a known behavior with SailPoint ISC workflows.

Any help would be appreciated.

2

Hi,

Even we are seeing this behavior in our tenant recently. We have raised Sailpoint support ticket for the same. It was working fine till last 2 weeks

3

Thanks for confirming. I have also raised a ticket with vendor for this issue. I will share any updates I receive here.