HTTP 409
resource_not_ready — Shorty API error
Resource not ready (HTTP 409): when the Shorty API returns the resource_not_ready error, why, and how to fix it.
| Code | HTTP status | Type URI |
|---|---|---|
resource_not_ready | 409 | https://aishorty.com/docs/api/errors/resource_not_ready |
When it happens
The resource exists but is not yet in a usable state — e.g. downloading a subtitle artifact before its job has finished.
Example response
{
"type": "https://aishorty.com/docs/api/errors/resource_not_ready",
"title": "Resource not ready",
"status": 409,
"detail": "The subtitle artifact is not ready — the job is still running.",
"instance": "urn:request:req_01J9Z8ABCDEFGH0123456789",
"code": "resource_not_ready",
"request_id": "req_01J9Z8ABCDEFGH0123456789"
}How to fix it
Poll GET /v1/jobs/{id} (or use the SDK jobs.waitFor) until the job reaches a terminal state, then retry.
Related errors
- resource_not_found
Resource not found (HTTP 404)