Troubleshoot workflow imports
Review common workflow import issues and their resolutions.
| Issue | Cause | Resolution |
|---|---|---|
| Missing resource references | Credential, integration, or large language model (LLM) IDs in the imported workflow do not exist on the target instance. | Open the affected steps and reconfigure the credential, integration, and LLM fields to use resources available on this instance. |
| Invalid file format | The selected file is not valid JSON, or contains syntax errors. | Verify the file contents. Check the line number in the error message and correct the syntax. |
| Schema version mismatch | The source instance uses a different automation orchestrator schema version than the target instance. The current schema version is2.0.0. |
Export the workflow from an instance that uses the same schema version. |
| Missing node types | The workflow references node types not available on the target instance. | Verify that you configured the required integrations and node types on this instance. |
| Cycle detected | The workflow definition contains a circular path between steps. | Open the workflow in the canvas and remove the edge that creates the cycle. |
| Unreachable steps | One or more steps are not connected to any trigger. | Connect all steps to a trigger through at least one path. |
| Invalid edge references | An edge references a step or trigger that does not exist in the definition. | Verify that no one manually edited the exported file. Re-export from the source instance. |
| Name conflict | A workflow with the same name already exists in the target project. | Choose a different name or import into a different project. |
| File too large | The file exceeds the 10 MB maximum. | Reduce the file size or verify you are uploading the correct file. |