Skip to main content

UNSUPPORTED_TX_FIELD

The transaction carries a fee-relevant field this Relay-Unit schedule does not price.

HTTP status422
GroupPricing and purchase
RetryableNo — sending it again changes nothing

What happened​

If a protocol upgrade adds a field that changes what a transaction costs, CoRelayer refuses it until a schedule version that prices it is active — rather than guess and under-charge.

What to do​

Remove the field, or wait for the schedule version announced in the changelog.

The problem document​

Every error is application/problem+json (RFC 9457) with the same shape:

{
"type": "https://docs.co-relayer.com/errors/unsupported-tx-field",
"title": "The transaction carries a fee-relevant field this Relay-Unit schedule does not price.",
"status": 422,
"detail": "A sentence about this specific occurrence.",
"instance": "req_01JB…",
"code": "UNSUPPORTED_TX_FIELD",
"retryable": false,
"hint": "Remove the field, or wait for the schedule version announced in the changelog."
}

See the error model for what each member means and how to handle unknown codes.