Skip to main content
Inspect both the HTTP status and the GraphQL response. HTTP 200 can contain GraphQL errors, and data can be partially present alongside errors.

Read the error envelope

An illustrative field-error response is:
Example error response
Application error codes appear as numeric prefixes in message. Do not assume they are available as extensions.code. The path, message text, and extension type depend on where the failure occurs; transport-level rejection can return data: null and a different path.

Choose the next action

A generation error may concern prompt moderation, incompatible media, a quality/duration/reference combination, credits, or concurrency. Correct the reported cause. Do not bypass moderation or permission checks by switching accounts or retrying an unchanged request.

Preserve partial receipts

If a mutation’s response contains a content ID or task ID alongside an error, save those IDs. A failure while resolving a selected response field can happen after creation. Continue through tasks and results to establish the existing operation’s outcome. For account and workflow preparation, see the troubleshooting guide and credits and billing.