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.
Monitor provisioning failures through Account Activities or provisioning error events instead of relying solely on the Provisioning Completed trigger.
Consider using external monitoring/reporting on failed provisioning transactions and creating tickets based on those failures.
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.
Are you using any filters for Provisioning Completed tigger?
Workflow is not getting triggered even without using any filter?
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
Scheduled trigger - schedule it to run every 24 hrs
HTTP Request - call search API where you can use above search
Loop - iterate through each of the event result from step 2
HTTP Request - inside loop to call create ticket API
Currently, there is no filter configured for the Provisioning Completed trigger, and the workflow is not being triggered either way. The screenshot I shared shows the error received when a Create Account operation failed event.
I’m considering using the Scheduled trigger you suggested as an alternative. I’ll discuss this possibility with my team and see if that would work for us.
I’ll discuss these possibilities with my team and consider opening a SailPoint Support ticket to get a clearer understanding of how this connector provisioning event behaves.
Hi @thiago-ferreira Thing is, it’s not attempting to provision, it’s failing on a unique account attribute transform so it hasn’t started the provisioning process. You may want to consider a different way of generating the failure. Maybe hard code a sAMAccountName that already exists.
Thanks for your reply! That’s exactly what I had in mind. I’ll discuss it with my team and run a few different tests to see whether this approach will meet our needs.
