Cannot open flow

[ZachOnNow]

Hello everyone, I can no longer open my flow I keep getting this error message: Your flow cannot be found. Flow sys_id:An

I have no clue why this is happening, I have not edited my flow in a couple of days.

Maybe the cause is that my PDI was moved to the new data center.

Any ideas/help is much appreciated!!

[scottl]

Really, did you ever contact HI Support about it?

I've now had to delete and recreate this flow 3 times already, now by the looks of it, it will now be a fourth time.  I've tried all the suggested fixes without any luck. SN knows of the problem too, yet pass it off as "your problem" because they believe it's to do with migration into other instances as stated by their own "help" article. Clearly it's not, and SN did zero investigation to actually fix it and just repeated someone else's community post.

Added: And what's the bet the issue arises from the way SN hi-jacks the browser's ability to use tabs, with SN thinking they know best about displaying tabs within a window instead of allowing the browser to do it, like everything built in this "NEXT" experience. Where the session of other opened Flow windows breaks the "version" somehow even without editing it.

[scottl]

Update: 3 hours later, it just crashed again. After I had recreated everything. Lost all my work. On Save, it was stuck on trying to save.  Waited.  Waited more. Reloaded the page, and it gave the Modal of d3ath...

"Your flow cannot be found. Flow sys_id:n"

Anyone from SN care to explain, what is going on?

[scottl]

Update: There is a serious bug when creating and editing subflows, and SN is well aware of it but it won't be fixed until at least the end of Jan, 2025!  

If you add an Action "Get Catalog Variables", save it, then add an action "Assign Subflow Action" it completely corrupts your flow, and can even delete your activities within it. The "proposed solution" for the known problem PRB1811296, does not offer a fix for flows that have had their activities deleted, only those that still have their activities.

Their KB "KB1709941" article is also incorrect, as this can happen on existing flows. 

To think that saving your flow as you work, now corrupts your flow entirely, is just unreal.   And that's not mentioning the corruption that can also occur in decision tables where it can delete the values in referenced fields by itself without any record of it happening. With SN admitting that the data was deleted and lost but because the company did not allow SN to replicate the instance remotely to find out what happened, SN proceeded to ignore the issue and closed the Support ticket. 

This is where we're at, and just sums up SN right now.  

Version: Xanadu - Patch 2