Task guide

Troubleshoot an import or missing flow

Check identifiers, endpoints and access before retrying.

Before you start

Prerequisites: The source or diagram that failed, with a backup copy.
Permissions and plan: Local checks require no account. Publishing requires an active account.

Steps

Check that you are using a desktop browser with a window at least 960 pixels wide.
Choose Export & view → Import model and import the small example below to isolate a source problem.
Check IDs are unique and valid, and flow endpoints refer to different existing objects.
Use Fit and the appropriate breadcrumb or view to locate a relationship.
For sync or access failures, keep a JSON backup, check sign-in and permissions, and report the exact error through Support. For MCP, verify read access with list_diagrams first.

Runnable example

Flowboard Markdown

Copy this model into Import in the editor. Export current work first. The two stable identifiers, api and db, connect the services to the flow.

# Request path

- API {#api type=service x=100 y=120}
- Database {#db type=database x=500 y=120}

## Flows
- api -> db {#requests label="requests" color=#f05a47 speed=1 direction=forward}

Change a label to describe your system. Keep the identifiers the same when you want existing connections to keep referring to those nodes.

Check your work

Expected outcomeYou can isolate a source problem from an account or service problem.

Next steps

Try the workflow in the editor, then use the reference for control details and model syntax.

Open the example or setup page Detailed reference

If a step does not work, keep an export of your model and follow the troubleshooting guide. Include the error message when contacting support, without sharing credentials or private architecture.