Flow Designer- Error- Resetting Stack

[Puru2]

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.

[SumanthDosapati]

@Puru2 

You can check below points :

1. Setting the flow to run as 'system user' / 'user who initiates the session'
2. Check the 'Restricted Caller Access Privileges' (sys_restricted_caller_access) table to see if any of the status is requested/denied/invalidated.
3. Check 'sys_scope_privilege' table to see if every thing is allowed for relevant records.
4. Check if application access on your custom table is set to All Application scopes with can create/read/update is enabled.
5. Finally the role mapped to create ACL on your custom table should be given to the user 'Run as' in the Flow properties.

If none worked, and since it came after an upgrade, would suggest you to create a support case with ServiceNow as no relevant known error articles are also present.

Regards,
Sumanth

[Ankur Bawiskar]

@Puru2 

did you try running the flow as System User?

Did you try to test the flow using TEST button?

If my response helped please mark it correct and close the thread so that it benefits future readers.

[A_Stembreit]

I am also getting this error in a Yokohoma instance. It is logging for every flow execution, but is not currently causing any issues other than just being a concerning message during the daily log review. 
All flows are set to run as 'System User' and this is occurring in flows that do not access custom tables. 
Following this issue, hope it gets resolved soon.  

[brumiou]

same on our side 😞