Your Compute job looks stuck
How to tell whether a job that looks stuck is waiting for capacity or for checking, and what to do next.
Refresh the existing job
Your job has not changed as expected. Read that same job in the correct account instead of submitting it again. Note when you checked and retain the returned state and state version.
An unchanged screen may reflect slow work, a stale view, or an unavailable read. It does not prove that the job stopped or that a new submission is safe.
Separate the branches
- Current nonterminal state: follow the client's supported polling or event path. Keep the existing reference and avoid rapid parallel polling.
- Read unavailable or access refused: resolve the read or account problem. Do not treat missing information as zero progress.
- Partial output exists: inspect its recorded outcomes and coverage. A partial file is not automatically the final result.
- Terminal outcome returned: follow that outcome's result, refusal, or failure guidance. Do not keep waiting for a successful state that was not reported.
The job read and event history are observations of the same work. An event or progress message is not authority to change the quote, budget, or destination.
Check timing without inventing a deadline
Compare the job's agreed requirements with the current observation. A local HTTP timeout and a quote's expiry are not the job's completion deadline. Do not turn an example duration into a service guarantee.
If you need to stop work, use only a supported cancellation control for that job. A cancellation request is separate from confirmed cancellation and any already accepted work. Never terminate a provider machine or weaken a security check as recovery.
Continue or ask for reconciliation
Continue when the current state and permitted next action are clear. Stop automated writes when progress, cancellation, or the existing outcome is uncertain.
Use Contact Lithi with the job reference, latest safe state and version, the times you observed it, and the client version. Leave out input files, generated content, credentials, and signed URLs. For an unresolved initial submission, use submission recovery.