RTBlintAlpha
RTBResponse has no id
The response carries no id, so the orchestrator cannot tie the mutations back to the extension point call it made.
What it means
RTBResponse.id is absent or empty. It is how a response is correlated with the RTBRequest that produced it.
Why it matters
An orchestrator calls several agents concurrently within one auction. Without the id it cannot attribute mutations to the agent that proposed them, which breaks both the accept/reject decision and any later audit of who changed what.
How to fix it
Echo the id from the RTBRequest verbatim.
Example that trips it
{ "mutations": [], "metadata": { "api_version": "1.0.0" } }Check your payload
Paste a bid request or response into the tester to see whether this code fires against it, or gate on the id in CI with the CLI: the id is stable, wording is not.
Back to the full diagnostic code reference.