Skip to main content

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 symptomStart here
Model evaluation or generation reportReading Markdown Reports, Troubleshoot First Run, and Diagnostics Catalog
Order null/NotLoaded, full relation or result-carrier mismatchOrder API Usage and the selected native troubleshooting table above
Order stale write, native COMMIT failure or resource cleanupOrder failure diagnosis; preserve native errors and the existing pending-release qualifications
Missing generated methodTroubleshoot First Run
Missing query purpose/comment or mutation auditDiagnostics Catalog
Java generated-code debuggingDebugging Generated Code
Java SQL/logging behaviorDebugging and Logging
Java slow requestsProfiling
Java memory or connection pressureOOM and Connection Leaks
Rust type inferenceType Inference Errors
Rust logging/tracing gapsObservability and Tracing
Rust concurrency or deadlockConcurrency and Deadlocks
Version/provider migrationUpgrade 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:

  1. Source model.
  2. Generator/client configuration and version alignment.
  3. Handwritten application or extension code.
  4. Runtime/provider configuration.
  5. 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.