RTBlintAlpha
Mutation op is not an ARTF Operation value
The operation is outside the enum, so the orchestrator cannot tell whether to add, replace, or remove at the target path.
What it means
op carries a value outside OPERATION_ADD, OPERATION_REMOVE, and OPERATION_REPLACE, and is not one of the document's lowercase spellings either.
Why it matters
The path says where and the payload says what; the operation says which of three quite different things to do with it. Guessing between adding a deal and replacing the deal list is not a guess an orchestrator can safely make.
How to fix it
Send an enum value name or its number.
Example that trips it
{ "intent": "ACTIVATE_DEALS", "op": "OPERATION_UPSERT", "path": "/imp/imp-1", "ids": { "id": ["deal-2"] } }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.