Result or file unavailable
What to do when a finished result or its file will not open or download, and how to ask for it again.
Open the existing result record
A result file is missing, a link has expired or a download failed. Start with the original job's result read in the correct account. Keep the artifact reference rather than submitting the work again.
For REST, GET /v1/jobs/{id}/result reads the encrypted result and delivery metadata with authorized jobs:read access. Use the supported client for any subsequent transfer or verification.
Follow the observed problem
- Work is not complete: read current job state. A missing final file is not yet a download failure.
- Download permission expired: request renewed access to the existing artifact through the supported result path. This does not start a new inference run.
- Access is refused or the result is not found: verify the account, reference, and current permission. Do not infer erasure from the response alone.
- Transfer failed: preserve the artifact identity and use the supported transfer recovery. Never paste the signed URL into logs or a ticket.
- Bytes or integrity do not match: stop using the file and retain safe expected and observed verification details. Do not treat a successful HTTP download as proof of the correct artifact.
Check what you received
Use the result's declared size and integrity information where provided. Match the artifact to the intended job and inspect the outcome records before relying on the accepted data. Do not create a signature or checksum merely to make verification pass.
A valid receipt does not prove the business meaning of every answer. An expired link also does not establish deletion from storage, backups, or a destination that already received a copy.
Confirm or escalate
Success is access to the intended existing artifact with its required checks satisfied. Stop when ownership, integrity, or retention is unclear.
Use Contact Lithi with the job and safe artifact reference, error code, client version, and observation time. Leave out signed URLs, credentials, private result content, and full payloads. For an external destination problem, use delivery Help.