Flow execution is cancelled upon receiving request
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2023 02:25 AM
Hello everyone.
We have created a new flow with flow designer for change request. Once, we've received the following error:
Flow Designer: Flow execution is cancelled upon receiving request. Reason is Aborting engine execution, cancel requested in same txn in which flow is running.
Anybody can help us with this error? We don't know why the flow was cancelled because the trigger conditions are correct. what object is invoking the error? business rule or the flow itself?
Thank you very much.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2024 07:24 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2024 05:53 AM
The solution I included in my previous posts is what I left in place. The reply below from "gjz" could possibly solve this situation for you, too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2024 07:56 AM
Thank you @Tim Deniston . That worked for me 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2024 09:44 AM
For anyone else looking for a solution - I did find a simple one.
In my flow, after the approval request, I check to see if the request was approved and if not, I end the flow. I discovered I had the stage set just before the IF step, which means it was always set. Once I changed the stage to the steps executed after the if, the flow started working again. The business rule "cancel flow on request cancelled/deleted" checks for the stage and is responsible for cancelling the flow.
Here is a screen shot of my before and after:
This caused the flow to cancel:
Flow works correctly:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2025 09:16 PM
Had this error pop up too. I found that just removing the Request Cancelled flow stage from the flow and entering it as a field update on the Item was enough to fix it.