Provisioning Completed Trigger is not working for Create Account failed operation on Active Directory

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

Hello,

I’m experiencing an issue with the Provisioning Completed Trigger in a workflow.

I need the workflow to be triggered when a Create Account provisioning operation fails on an Active Directory direct-connected source, specifically due to connectivity issues.

The goal is for this workflow to create a ticket for the Help Desk team via an HTTP Request whenever this type of provisioning failure occurs.

However, when I simulate a connectivity failure by making the Active Directory server unreachable, I receive the corresponding provisioning error event, but the Provisioning Completed Trigger does not fire, and the workflow is not triggered.

I would like to know whether this is expected SailPoint behavior or if there is any configuration, workaround, or other approach that would allow the workflow to be triggered in this scenario.

Any guidance on how to handle this type of provisioning failure would be greatly appreciated.

Captura de tela 2026-08-31 140547
Captura de tela 2026-08-31 140547731×353 23.8 KB

2
  1. Monitor provisioning failures through Account Activities or provisioning error events instead of relying solely on the Provisioning Completed trigger.
  2. Consider using external monitoring/reporting on failed provisioning transactions and creating tickets based on those failures.
  3. Open a SailPoint Support ticket to confirm whether your specific connector and provisioning path are expected to generate a Provisioning Completed event for connectivity-related failures, as behavior can vary by connector implementation.
3

Hello @thiago-ferreira , Welcome to developer forum!!

  1. Are you using any filters for Provisioning Completed tigger?
  2. Workflow is not getting triggered even without using any filter?
  3. Check if there are any events/account activity generated for the failure in search? you can use this search query type:PROVISIONING AND status:failed AND created:[now-1d TO now]

Other way to achieve is using scheduled search and HTTP Request to call search API. High-level steps

  1. Scheduled trigger - schedule it to run every 24 hrs
  2. HTTP Request - call search API where you can use above search
  3. Loop - iterate through each of the event result from step 2
  4. HTTP Request - inside loop to call create ticket API
4

@thiago-ferreira you the below filter

image
image1318×285 39.6 KB