Compute job did not run
How to tell whether your job was refused, accepted or left uncertain, and what to do before you retry.
Look for the existing job first
You submitted work but cannot see it running. Keep the response or reference already returned, and read that job or batch in the correct account before submitting anything else. A submission acknowledgment is not completion. A timeout is not proof that nothing started.
Match the observable outcome
A job reference exists: read its current state. The REST job read uses GET /v1/jobs/{id} with authorized jobs:read access. Your supported client may provide the same read. Keep the returned state and version together.
The request was explicitly refused: resolve the named authentication, input, quote, policy, or availability problem. Confirm that you are looking at this submission, not an earlier attempt.
The response was lost or only reports a connection error: the outcome is unknown. Preserve the original intent and idempotency identity in protected client records. Do not replace them with a new key just to make the request appear fresh.
No matching job is visible: verify the account and reference. A missing result under one credential does not prove that the job never existed. Stop automatic submission if you cannot reconcile it.
Retry only the same authorized intent
Use the documented replay behavior of the exact operation. Keep the payload, account, quote and destination unchanged when the attempt is a transport retry.
For example, if your client timed out after submission, keep its original request identity and check the existing job before deciding whether the operation's documented replay applies. See idempotency and retries for the recovery sequence.
A deliberate new job needs its own current review and applicable approval. First establish that it will not duplicate work already admitted. If the original job is running without useful progress, use stalled work Help.
Confirm or escalate
Success is a known existing job state or a confirmed refusal with its next action resolved. Stop when admission remains unknown.
Use Contact Lithi with the operation, time with time zone, safe error code, client version, and existing job or request reference when available. Say that submission may have succeeded. Do not send the full request, credentials, or signed transfer URLs.