Value payload does not match the declared intent
The mutation sets a payload member the intent does not carry, such as adjust_bid on a deal activation.
What it means
Exactly one payload member is set, but it is not the one the intent uses. The finding names the member the intent expects.
Why it matters
Intent and payload are the two halves of what is being proposed, and when they disagree the orchestrator has no basis to prefer one. It usually surfaces when a mutation builder is copied between intents and the payload construction is not updated.
How to fix it
Set the member the intent carries. ADD_CIDS is the only intent that accepts more than one, ids or content_data.
Example that trips it
{ "intent": "ACTIVATE_DEALS", "op": "OPERATION_ADD", "path": "/imp/imp-1", "adjust_bid": { "price": 4.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.