Troubleshoot an import or missing flow

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

1. Try importing the small example below to establish that the editor works.

2. Check that every ID in your source is unique and begins with a letter; use only letters, digits, underscores and hyphens.

3. For a missing flow, check that from and to refer to different existing node IDs.

4. Use Fit, then open the appropriate level: a valid relationship may belong to another view.

5. If publishing fails, keep a local export, check sign-in and write access, and contact support with the error message, browser and reproduction steps. Exclude private source and credentials.

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.

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.