MC-1 DOCS
API ReferenceCookbook
Docs/Operations/Troubleshooting
PublishedGuidanceLAST REVIEWED · 30 AUG 2026

Troubleshooting

Diagnose authentication, eligibility, streaming, policy, and integration failures.

Triage order

  • Confirm API base, key scope, and project.
  • Validate request shape and logical model.
  • Inspect policy, privacy, region, provider, and model eligibility.
  • Check provider health and deployment configuration.
  • Compare streaming and non-streaming behavior.
  • Retain safe request identifiers and exact timestamps.

Common failure patterns

  • 401: missing, expired, or wrong-scope key.
  • No eligible route: constraints exclude every configured path.
  • Required evaluation unavailable: fail closed or request review.
  • Harness tool loop fails: verify role, tool-call ID, and continuation shape.
  • Unexpected cost: inspect volume, context, retry, escalation, and provider mix.
End of guide
Was this page helpful?