- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2024 01:12 AM
I have created this workflow since 2023 and it worked on my PDI (Tokyo release). However, it does not work on my new PDI (Washington DC release).
This is just a simple workflow to trigger approval for caller when his/her Incident is set to 'Resolved' state by a support staff. More details about the workflow can be found in the screenshots. Has something been changed in new releases recently?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2024 07:43 PM
I found the root cause. We need to set 'Run the workflow always' for 'If condition matches' field.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2024 01:29 AM
1.There might be deprecations in favor of Flow Designer, which is now the preferred automation tool.
I would also suggest to use the Flow Designer in this case
2.Use Flow Designer’s debug feature to pinpoint any issues
3.Confirm Roles and Permissions:
- Ensure the caller has appropriate permissions for approvals.
- Verify the support staff’s actions do not bypass or conflict with the approval process
4.Switch to Flow Designer: If workflows are deprecated in your version, transition to Flow Designer for future-proof automation.
If you Found this answer is helpful please mark this as helpful
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2024 02:03 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2024 02:08 AM
Thanks @Arun_Manoj for your quick response, I checked, I can confirm that the workflow version is still the newest one and the workflow is published.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2024 03:48 AM
Hi @dhuynh28 ,
There can be many reasons behind it need to find it step by step,
check if the workflow is triggered.
try to validate the workflow on new instance , see if there is any error.
Run a test on workflow to see how it goes, attach to catalog and raise request.
The table on which the workflow is attached is active or not
check if the workflow is active to be used.
☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....