I wrote a flow using flow varibales and set subflow outputs when i saved and opened it getting error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2025 11:13 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2025 03:49 AM
Hi @udaybura,
I’ve run into this before too. It usually happens when the flow glitches and assigns a bad sys_id. Check out this KB article: KB1792379.
What worked for me was going into the Flow Logic Instances table and deleting the most recent record created at the time of the error. After that, I was able to open the subflow again.
Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2025 04:11 AM
I encountered this error when adding flow variables to an existing flow/subflow. The ultimate fix is to upgrade the Flow Designer plug-in to the latest version (fixed in v26.3 which requires Xanadu patch 5 or greater). You can recover the last working version of the flow following these steps:
- In the Flow Designer / Workflow Studio main page that lists the flow/subflows/actions, click the information icon (i in a circle) beside the flow causing issues and copy the sys_id from the details shown.
- Navigate to sys_update_version.list and search on Names containing the sys_id
- Revert to a previous (working) version of the flow
Another possible workaround for opening a flow that already has this error is found here
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1709519