Flow Designer- Error- Resetting Stack

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-19-2025 03:02 AM
Hello All,
While working with Flow Designer in SN- Yokohoma release, recently we have been facing the following error:
"Found mismatch in scope after flow engine done. resetting stack".
Flow Designer calls an action, which further creates a record in a custom table.
The messages from log-statement show that after obj.insert() operation, sys_id of the new custom-record was generated, however the record with the aforesaid sys_id was not found in the custom table.
It appears like system has reverted the Create operation.
Following is the step-by-step operation:
Submit Catalog Item through Service Portal -> Flow Designer -> Action -> Script Include
All the mentioned objects are in the same scope, which is Global -> RITM record, Flow, Action, Script include.
This Flow-Designer is working in Washington release; however, it has stopped working in Yokohoma release with the following warning: "Found mismatch in scope after flow engine done. resetting stack".
Please let me know for any valuable suggestions.
- 4,568 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-23-2025 07:19 AM
Same here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-05-2025 01:18 AM
Hi @Puru2 ,
Please look for any Query BR on the custom table which may be hiding the records.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-26-2025 01:04 AM
I got the same error but the flow did complete. In my action am running a powershell script.
will try to figure out the fix and will share it here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-24-2025 08:30 AM
Anyone has any solution to this so far? Anyone created support ticket already?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-29-2025 09:52 AM
Anyone has figured out a fix for this? We have the same warning and we are also using powershell script