404 — resource not found

Body: {"success": false, "message": "Resource not found."}; for link issuance — {"success": false, "message": "File not found."}. Nothing was created or changed.

Either the identifier does not exist (a typo in the UUID, an id in the wrong format), or the resource was deleted. POST /storage/url has a third cause, the most common one: the retention period of the order has expired — by default 7 days after it reaches a terminal status. For GET /orders/chunks/preview, a 404 is not an error at all: it means "this text is not in the cache, send the full text via POST".

Check the identifier against its type: orders and templates use UUIDs, chunk previews use a 64-character sha256, external voices use the provider identifier. Storage trap: after retention expires, GET /orders/{order} STILL shows the old paths in result.files[] — the user-facing response has no separate expiry flag, and a dead path shows up only as a 404 on download.

GET /orders/{order} — whether the order exists and what status it is in. If the order is there but the 404 came from POST /storage/url, the problem is file retention.

• storage_expired — files deleted by retention
• Guide: files and storage
• POST /storage/url
• GET /orders/{order}