Skip to main content

Access was rejected

Confirm the connected APOB account and the access method expected by your client. Check whether its API key has expired or been revoked, or whether its OAuth connection needs authorization again. Authentication does not grant access to another account’s private media. See access and authentication.

Upload verification failed

Check that the original bytes were uploaded before the transfer URL expired, using all supplied headers. Compare the file’s size, MIME type, and checksum with the upload preparation. Retry completion for the existing upload within its allowed verification window. See prepare your media.

Generation timed out or the response was unclear

If the client has a task identifier, read that task’s current result. A timeout in the client does not establish that the operation stopped on the server. If no identifier was received, inspect generation history in the same account before considering another submission. Keep the time, operation, and any receipt you have so you can correlate the request.
An uncertain submission is not safe to retry automatically. A repeat can create another generation and consume credits again.

A status read failed

Retry the read using the same task identifier. Do not turn a read failure into a new generation. A failed result read and a failed generation are different outcomes.

The task finished without a successful result

Review the reported outcome and the selected workflow’s inputs, credit eligibility, and moderation requirements. A blocked or failed task is a terminal outcome, not a successful generation. Changing clients does not remove these requirements. Retrieve the completed task’s result again for a fresh output link. Download the existing result rather than submitting another generation. If result retrieval still fails, keep the task identifier and the observed message for investigation.

Gather useful diagnostic information

Record the operation, approximate time and time zone, task or content identifier, client, and the safe error message you observed. Check generation history and billing activity in APOB when the submission may have been accepted or automatic reload was attempted. When sharing diagnostic information, remove API keys, access tokens, signed URLs, and private media. Review credits and billing before attempting another paid operation.