Troubleshooting Index
Start with the visible symptom and preserve the first complete error. Do not patch generated source merely because a compiler points at it.
For an Order failure, choose the language table first: Java, Rust, TypeScript, Python, Go, C# / .NET or Swift. Each linked authority keeps its recorded version and release qualification. This index is a navigation review, not a new runtime compatibility claim.
By Failing Stage
| Stage or symptom | Start here |
|---|---|
| Model evaluation or generation report | Reading Markdown Reports, Troubleshoot First Run, and Diagnostics Catalog |
| Order null/NotLoaded, full relation or result-carrier mismatch | Order API Usage and the selected native troubleshooting table above |
| Order stale write, native COMMIT failure or resource cleanup | Order failure diagnosis; preserve native errors and the existing pending-release qualifications |
| Missing generated method | Troubleshoot First Run |
| Missing query purpose/comment or mutation audit | Diagnostics Catalog |
| Java generated-code debugging | Debugging Generated Code |
| Java SQL/logging behavior | Debugging and Logging |
| Java slow requests | Profiling |
| Java memory or connection pressure | OOM and Connection Leaks |
| Rust type inference | Type Inference Errors |
| Rust logging/tracing gaps | Observability and Tracing |
| Rust concurrency or deadlock | Concurrency and Deadlocks |
| Version/provider migration | Upgrade Guide and Migration Notes |
Minimum Diagnostic Record
Before escalating, collect:
- exact command and working directory;
- complete Markdown report or first error;
- model revision;
- generator/client and runtime versions;
- selected language toolchain, framework, driver and provider versions;
- relevant scoped Assist signatures and application call site;
- whether the retained example/receipt already explains the same failure;
- the smallest unsupported operation, only if a new reproduction is needed.
Fix Order
Prefer fixes in this order:
- Source model.
- Generator/client configuration and version alignment.
- Handwritten application or extension code.
- Runtime/provider configuration.
- Framework or environment.
Use generated manifests, scoped Assist and compiler diagnostics to identify the right API. Do not search generated domain-library source for method discovery or patch it as the first response to a failure. Regenerate when the model or generation step needs correction; an editorial gap does not require regeneration.