I wrote a flow using flow varibales and set subflow outputs when i saved and opened it getting error

[udaybura]

I created a subflow and used flow varibales then i saved it is showing flow not found. then i created a subflow for testing then it also showing the same error why this error is coming and how to resolve it.

[M Iftikhar]

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. 

[Brad Bowman]

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:

1. 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.
2. Navigate to sys_update_version.list and search on Names containing the sys_id
3. 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