What to send when you ask for help

You want help without oversharing

A good support message is short and specific. Six facts resolve most Compute questions, and none of them is your data.

If you are unsure what to include, the answer is almost always in the response you already have.

Everything you need is in one response

Every Compute API response carries an envelope. Copy from it rather than describing what you remember seeing.

The envelope carries the request ID, the operation, the contract release, and the typed state. It also carries the evidence class, the observed time, a validity window, and a structured next action.

Take the values verbatim. A paraphrased error code sends the conversation down the wrong path.

Send exactly these

1. The request ID from the failing response.
2. The operation name, exactly as the envelope states it.
3. Your client version and the contract release the response reports.
4. The safe error code and typed state, copied verbatim.
5. The time you saw it, with the time zone.
6. What you expected instead, in one sentence.

A job or batch reference helps when the question is about one specific run. So does the workflow ID and version.

Never send these

• Input or output payloads, or file contents of any kind.
• API keys, tokens, passwords, or the value behind a credential reference.
• Signed download or upload links. They carry authority on their own, to anyone holding them.
• Bank account numbers, card numbers, or payment credentials.

Support never needs any of them. If a message asks you for one, stop and report the message itself.

Where you must show a failing record, replace every value with a placeholder and keep only the shape.

What not to repeat

Never paste a full log dump and ask what is wrong. Logs carry request content, and sometimes carry credentials you did not know were in there.

Never open a second request for the same problem. Reply on the first one, because the request ID is what ties the history together.

Get help safely

Open one request with the six facts above, and keep the response envelope where you can reach it. Support will ask for the request ID first.

If you have already sent a key or a signed link to anyone, rotate or revoke it before you do anything else.