Safe diagnostics

A useful report links the observed behavior to a specific request or job. Start with identifiers and state. Most access, routing, and billing issues do not require sending the underlying learning passage or generated answer.

IncludeCopy Anchor Link

• UTC timestamp and the platform origin.
• Client language and, if relevant, workspace SDK version.
• HTTP method, route template, status, and error.code.
• The HTTP X-Request-Id and durable job ID when available.
• Authorized project ID, job status, phase, and last update time.
• Adapter version, candidate version, and activation outcome for routing issues.
• Whether the attempt reused the original idempotency key and unchanged body.
• Expected behavior and the shortest steps that reproduce the problem.

For a spending discrepancy, include the integer reserved and charged amounts and whether the job settled. For a payment discrepancy, include the order reference and selected project. Identify which screen or API response showed the unexpected value.

Leave outCopy Anchor Link

Do not include bearer tokens, full API keys, cookies, passwords, provider credentials, payment-card details, database URLs, or signed internal URLs. Redact learning sources, inference messages, completions, and raw reasoning from the initial report.

Avoid screenshots of an unmasked key dialog or a private result block. An opaque subject identifier is preferable to a subject name that itself reveals a customer's identity. Report that an idempotency key was reused, rather than exposing a key that encodes private application information.

Example reportCopy Anchor Link

UTC: 2026-09-24T10:00:00Z
Origin: https://convergingthought.com
Client: server-side TypeScript
Operation: POST /v1/internalizations
HTTP status: 202
HTTP request ID: <request ID>
Job ID: <job ID>
Latest status / phase: reconciliation_required / <phase>
Settled: false
Retry: no replacement submitted; original operation key preserved
Observed: job requires investigation and still holds its reservation
Expected: a known terminal outcome or a recovery explanation

This is a template, not a real incident. Substitute actual identifiers only in an authorized support channel. Keep your own private source and evaluation evidence available in case a later investigation specifically needs a minimal redacted example.

EscalateCopy Anchor Link

Contact team@convergingthought.com. Explain the affected workflow and include one recent request or job ID. Repeated blind retries create noise and can start additional paid work, so preserve the first operation while the issue is being investigated.

If the issue is a content-quality failure rather than transport or routing, first follow Knowledge troubleshooting. If the model operation is ambiguous, follow Job recovery and do not attempt to reconcile usage by guessing.