Troubleshooting
| Symptom | Check first | Next step |
|---|---|---|
| Connection refused | The server is running and the configured address is correct | Connections |
| Authentication fails | User, password, TLS and the selected authentication method | Authentication |
| Table not found | Database, schema, spelling and the active search path | Schemas |
| Transaction conflict | SQLSTATE and whether the entire transaction was retried | Transactions |
| Queries fail after one error | The connection still has an aborted transaction | Run ROLLBACK, then retry the intended operation |
| Particle not found | Module deployment, function name and supported runtime | Loading Particles |
| Particle fails | Input types, dependencies, permissions and execution limits | Particle limits |
| Query is slow | Query plan, record count, indexes and resource pressure | Performance |
| Data is missing after restart | The same data directory and persistence configuration were used | Durability |
Capture useful information
Section titled “Capture useful information”Record the server and client versions, the failing operation, its error code and a minimal reproduction. Remove credentials, customer data and private identifiers before sharing diagnostics.
Check health
Section titled “Check health”curl --fail http://localhost:7173/healthA healthy response shows that the endpoint responds. It does not prove that every query or external dependency is healthy.