Compute Help
Your Compute job looks stuck
A Compute job has not moved for a while? Read the canonical status and its update time, tell a capacity delay from a verification delay, and act without resubmitting blindly.
The job has held the same state longer than you expected.
The job has sat in one state too long
You are watching a job that will not move. You want to know whether it is working, waiting for something, or already finished badly.
The answer is in the canonical status, not in the view you happen to be looking at.
Read the status and its update time
Ask for the job status directly. The response envelope carries the observed time and a validity window, so you can tell a fresh reading from a cached one.
Two facts matter: the current state, and when it last changed.
Job states are ADMITTED, RUNNING, AWAITING_REVIEW, PARTIAL, CANCELLING, CANCELLED, FAILED and SUCCEEDED. Beneath the job, each stage carries its own state, including BLOCKED, READY, MATERIALIZING, RUNNING, VERIFYING, AGGREGATING, SKIPPED and the terminal ones.
Then do this
Three delays look identical from outside and need different responses.
- Capacity delay. The job is ADMITTED or RUNNING and its stages sit at READY or MATERIALIZING. Current capacity is the constraint. Compare the elapsed time against the deadline you set in limits, then wait or cancel.
- Verification delay. A stage reads VERIFYING or AGGREGATING, or the job reads AWAITING_REVIEW. Stronger quality presets do more independent checking, and a review may be waiting on a person. Find out who that person is.
- Terminal delay. The job already reached FAILED, PARTIAL or CANCELLED and your view is stale. Read the status again and follow the next action it carries.
If you no longer want the work, cancel it. The job understands CANCELLING and CANCELLED; it does not understand being abandoned.
What not to repeat
Never resubmit blindly. An exact replay of the same request returns the earlier result, and the same identity with a different digest is treated as equivocation and refused.
Neither outcome makes the first job finish sooner, and the second one costs you the clarity of a single job to talk about.
Get help safely
Send the job reference, the request ID from your status call, and the operation name. Add your client version, the contract release, the state you observed, and how long it has held.
Leave out payloads, key values, signed URLs, and banking information.
Read more about job status and events and deadlines and capacity.
Still blocked?
Open the related help article or contact Lithi.