Your Compute quote expired

Your quote is no longer valid

You tried to submit against a quote and admission refused it, or the quote simply aged out. The typed state is REPLAN_REQUIRED.

Every quote carries an expiry and a signature, and it is marked non-authorizing. It never authorized work on its own, so nothing ran.

Check the current input and policy

Compare the request you are submitting now against the one you priced. Six things decide whether a quote still describes it.

• The workflow ID and version.
• The input snapshot: its version ID and content digest.
• The parameters you passed.
• The quality preset.
• The policy profile.
• The limits: your deadline and your maximum price.

A changed snapshot digest is the most common cause. A new file version is a new input, even when the name and the row count look the same.

Then do this

1. Quote the request again, exactly as you intend to run it.
2. Read the new maximum price and deadline on the quote before you go further.
3. Get approval again. Approval is always a separate act from quoting.
4. Submit against the new quote.

If your organization approves spend by policy rather than job by job, that policy still has to cover the new price. Check the current spend and approval state if the price moved.

What not to repeat

Never submit changed work against an old price. The old quote priced a different request, and admission is right to refuse it.

Do not resubmit the same request repeatedly after REPLAN_REQUIRED. It refuses the same way each time, because the drift it detected has not changed.

Do not edit a quote in place. There is no such operation, and a quote you could edit would not be worth having.

Get help safely

Send the request ID from the refused submission, the operation name, and the typed state. Add your client version, the contract release, and the time with its time zone.

Leave out payloads, key values, signed URLs, and banking information.