FAQ: Why does a flow I imported from another org shows validation errors?


Importing a flow from an outside organization may require some configuration updates; even if you have items such as data actions with similar names. This issue may occur because the back end GUID does not match, and subsequently the actions are not automatically picked up in the new org.

Until you update any configuration issues, Architect returns validation errors in the flow.