OHGROK / Integration guide
Troubleshoot a request
Find the failing step before retrying.
On this page
Keep the evidence
Capture HTTP status, response body, model ID, group, timestamp and any request/task ID. Remove Authorization and other secrets before sharing logs. An error category may use different status codes across upstreams; read the message as well.
Common failure patterns
| Symptom | What to check |
|---|---|
| Authentication / 401 | Site key, Bearer header, revoked or expired key. |
| Access / 403 | Account access, model group and permitted models. |
| Bad request / 400 | JSON validity, exact model ID, endpoint and supported parameters. |
| Not found / 404 | Duplicated /v1, wrong operation or missing task. |
| Quota / 429 | Balance, group restrictions and upstream rate limits. |
| Timeout / 5xx | Saved task ID and console outcome before retrying. |
Retry deliberately
Do not retry authentication or invalid-parameter errors unchanged. For transient failures, use a bounded backoff and respect Retry-After when present. A fresh generation POST may create another billable operation; no universal idempotency guarantee is documented here.
For video, poll the original task ID rather than submitting again. Stop on terminal states. For interrupted streams, retain the partial output and surface the failure to your application.