# Workflow that is triggered when provisioning fails

**URL:** <https://developer.sailpoint.com/discuss/t/workflow-that-is-triggered-when-provisioning-fails/187739>\
**Category:** SHF Discussion and Questions\
**Tags:** identity-security-cloud, workflows\
**Created:** [November 7, 2025, 5:51pm UTC](https://developer.sailpoint.com/discuss/t/workflow-that-is-triggered-when-provisioning-fails/187739 "2025-11-07T17:51:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Menzowskii](https://avatars.discourse-cdn.com/v4/letter/m/e5b9ba/32.png) [@Menzowskii](https://developer.sailpoint.com/discuss/u/Menzowskii)\
**Post date:** [November 7, 2025, 5:51pm UTC](https://developer.sailpoint.com/discuss/t/workflow-that-is-triggered-when-provisioning-fails/187739/1 "2025-11-07T17:51:29Z")

</div>

Hi,

I am fairly new to workflows and am still learning technically but essentially we want to create a workflow in which is triggered when an access request provisioning failure occurs. I am using the following trigger “Provisioning Complete” with the following filter **$.accountRequests[?(@.provisioningResult == “FAIL”)]** Although when testing this trigger and replacing the JSON input of provisioningResult with **SUCCESS,** it still manages to trigger the workflow for some reason?

Below is some of the JSON input

“accountRequests”: [  
{  
“source”: {  
“id”: “4e4d982dddff4267ab12f0f1e72b5a6d”,  
“name”: “Corporate Active Directory”,  
“type”: “SOURCE”  
},  
“accountId”: “CN=Rob.Robertson,ou=csm,ou=sales,dc=helpco,dc=com”,  
“accountOperation”: “Modify”,  
“provisioningResult”: “SUCCESS”,

I have also read another post in which the trigger filter **$.accountRequests[?(!(@.provisioningResult == “SUCCESS” || @.provisioningResult==“committed”))]** was used, but that still always triggers the workflow

---

<div class="post-metadata">

**Author:** ![davidtrn](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/davidtrn/32/19752_2.png) [@davidtrn](https://developer.sailpoint.com/discuss/u/davidtrn)\
**Post date:** [November 7, 2025, 6:38pm UTC](https://developer.sailpoint.com/discuss/t/workflow-that-is-triggered-when-provisioning-fails/187739/2 "2025-11-07T18:38:31Z")

</div>

Hello,

Are you testing using the test module in the workflow configuration ?

From my experience, the test will **always** trigger the workflow whatever the input you provide

---

<div class="post-metadata">

**Author:** ![MattUribe](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/matturibe/32/20300_2.png) [@MattUribe](https://developer.sailpoint.com/discuss/u/MattUribe)\
**Post date:** [November 7, 2025, 7:01pm UTC](https://developer.sailpoint.com/discuss/t/workflow-that-is-triggered-when-provisioning-fails/187739/3 "2025-11-07T19:01:06Z")

</div>

I agree - the test workflow feature always ignores the filter criteria.

---

<div class="post-metadata">

**Author:** ![Menzowskii](https://avatars.discourse-cdn.com/v4/letter/m/e5b9ba/32.png) [@Menzowskii](https://developer.sailpoint.com/discuss/u/Menzowskii)\
**Post date:** [November 7, 2025, 10:02pm UTC](https://developer.sailpoint.com/discuss/t/workflow-that-is-triggered-when-provisioning-fails/187739/4 "2025-11-07T22:02:54Z")

</div>

Ah ok I will try initiating an actual test within tenant in that case, thanks!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [January 6, 2026, 10:02pm UTC](https://developer.sailpoint.com/discuss/t/workflow-that-is-triggered-when-provisioning-fails/187739/5 "2026-01-06T22:02:55Z")

</div>

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