Errors and retries
Check both the HTTP response and the completion content. A safe failure message can arrive through a successful HTTP transport. Do not assume HTTP 200 means that research completed or that the request is chargeable.
- Authentication or access: check your API key and account permissions.
- Research scope: check the requested source collection, archive, or language.
- Worker startup: the service could not start the required worker within its startup deadline. This deadline does not cover the entire research request.
- General request error: the request did not complete. Preserve a sanitized request identifier and contact the workspace operator if it persists.
- Interrupted stream: the answer or final usage receipt can be incomplete.
Avoid automatic retries of an accepted chat request unless you can establish that the earlier request is no longer running. An ambiguous network failure can occur after the server accepts work; blind retries can duplicate work and cost. Never include an API key or private conversation content in a public bug report.