Troubleshooting

// Troubleshootingsymptom-first

Symptom-first diagnosis for the failure modes that show up during local development. Match what you see, then jump to the matching page.

Fastest path

Start with connectivity and config validity before deep logs. Most local failures show up there first.

Most FlowLayer incidents during development come from one of these areas:

• config loading and validation
• dependency planning
• readiness gating
• session connectivity and auth
• log retrieval expectations

Start from the page that matches what you see:

• Server Won’t Start
• TUI Cannot Connect
• Readiness Stuck
• Dependency Cycle
• Logs Missing

Fast Triage Sequence

1. Confirm the server is up and reachable from your client.
2. Confirm token and session target are correct.
3. Validate config before deeper runtime assumptions.
4. Identify the first failing or blocked dependency node.
5. Use logs to decide between restart action and config fix.

If the issue is still unclear, collect these before asking for help:

• exact server command
• exact client command
• first error line from server output
• whether Session API is enabled (-s or session.bind)
• whether auth failures are 401 or 403