Transaction Cancelled in flow designer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2025 02:56 AM
Hi Team,
I am experiencing a challenge with Flow Designer. We have created a flow that includes several sub-flows and actions, and it runs from Script Includes.
The code and design are the same in both Dev and PROD environments, but in PROD, when we run the flow, it shows as cancelled, and the logs indicate "Transaction cancelled."
below is from PROD:
I've noticed that the area highlighted in yellow above is taking more time.
Dev:
Could you please assist me?
Can you suggest alternatives besides increasing the run time?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2025 03:54 AM
@sainath3 please be aware that Yokohama has patches, so it might be a slightly different version even if both are Yokohamas...
As it affects the PROD environment, please raise a case for ServiceNow team to assist you.
- Navigate to https://support.servicenow.com/now?id=ns_guided_support
- click Create a case in the right-bottom corner
- you need access to the HI Portal, so you or the authorised person
Good luck and let me know the results
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2025 04:10 AM
PROD:
DEV:
Are there any differences between the Dev and PROD environments?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2025 04:15 AM
They're both the same version and patch, so 1:1
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Oi @sainath3,
Is this issue resolved, or what remains to be done?
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Hello,
The issue remains unresolved, and the processing time is longer than what we experienced in the Dev instance.