Skip to content
Skip to content

Delivery to your destination failed

If a finished result did not reach its destination, how to check what was written and retry delivery without rerunning the work.

Check the result before changing delivery

Compute returned a result, but the destination has not received it as expected. Read the original job's result and current delivery state before changing anything. Keep the artifact and destination references together.

A completed calculation and successful external delivery are different outcomes. Accepted output is not itself confirmation that an invoice was paid.

Resolve the delivery state

Pending or delivering: check the current state through the supported client. One slow observation is not a reason to start another copy operation.

Failed or access expired: ask the authorized destination owner to check the exact resource, required write permission, and grant expiry. Renew only the permission needed for the intended delivery.

Conflict or unexpected existing object: stop. Verify which immutable result the destination holds. Do not overwrite it or switch to another bucket, folder, or recipient as an automatic repair.

Delivered but the recipient cannot use it: check the intended artifact, recipient access, and required verification separately. A successful transfer is not proof that every downstream application imported the result.

Recover the existing artifact

Use a supported delivery recovery control when one is offered for that result. When no such control is available, contact Lithi with the existing reference. Do not invent a retry endpoint or upload plaintext to a relay.

An authorized download of the existing result may be an alternative. Changing destinations or processing requirements needs its own review; it is not the same delivery attempt.

Rerunning inference is not the repair for an otherwise valid stored result. Preserve the original work and charge evidence while resolving delivery.

Verify or stop

Success means the intended result reaches the approved destination and the required integrity and recipient checks pass. Stop when the previous delivery, destination identity, or permission remains uncertain.

Use Contact Lithi with the job, safe artifact or destination reference, current delivery state, error code, and time. Do not include storage secrets, signed URLs, private content, or banking details.

Still blocked?

Identity sync mapped the wrong person
How to fix a directory sync that created a duplicate, missed someone or gave the wrong role, before you change any access.
Need a person?
Tell us what happened and when.