Flow Designer Issue

[Nilanjan1]

Dear Experts... 

Did someone get into this issue, any way to resolved, reverting back to previous configuration has also not worked

[Ankur Bawiskar]

@Nilanjan1 

Did you receive this after migration?

From when did you start receiving the message?

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

[Nilanjan1]

Hi Ankur, 

This has happened previously and now after the upgrade it has happened again. I did go through some articles but reverting back to the previous version was suggested but it does not resolve the issue. 

[Josh Pirozzi]

It's a common error associated to a Flow not being saved, having an error within the Flow (one of the actions having an issue) or when the specific Flow or one of the associated Flow Actions being deleted.

If you have a version of the Flow saved in another Instance that doesn't display the error when you go to access it, I'd recommend creating an Update Set, making a minor update to the Flow and then migrate the Update Set into the impacted Instance.

If you don't have a working/accessible copy of the Flow in another Instance, then you'll most likely need to rebuild the Flow.

[Nilanjan1]

Thanks Josh. I am already rebuilding the new flow and created a separate update set to deal with this issue. If it is a bug it needs to be rectified. Else a small change in the catalog form may cause issues with the flow designer.

[Josh Pirozzi]

Sounds good - I've experienced this error a few times and usually it's related to a referenced Catalog Variable being changed without updating the Flow or a Flow Action that throws an error and doesn't allow me to access it anymore, making me think it was deleted. 

It's a strange/frustrating thing when it happens....