Skip to content
Cyoda Documentation
Settings

TRANSACTION_EXPIRED — transaction token has expired

cyoda-go version 0.6.2

errors.TRANSACTION_EXPIRED

Section titled “errors.TRANSACTION_EXPIRED”

NAME

Section titled “NAME”

TRANSACTION_EXPIRED — the transaction token presented to the proxy is past its expiry time.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 400 Bad Request. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

Transaction tokens are short-lived bearer tokens issued when a transaction is opened. This error fires when the token’s exp claim is in the past at the time the proxy validates it. The transaction itself may still be active server-side, but the token is no longer valid for routing.

Not retryable with the same token. The original transaction must be committed or rolled back before opening a new one.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.TRANSACTION_NOT_FOUND
  • errors.TRANSACTION_NODE_UNAVAILABLE

See also

Section titled “See also”
  • cyoda help errors — Every error response from the Cyoda REST API carries a structured errorCode in the properties object. Multiple codes may share the same HTTP status. Programmatic handling keys on errorCode, not HTTP status.
  • cyoda help errors TRANSACTION_NOT_FOUND — The transaction ID supplied in the request does not correspond to an active transaction. The transaction may have been committed, rolled back, expired, or may never have existed. Also occurs when a request is mis-routed to a node that never opened the transaction.
  • cyoda help errors TRANSACTION_NODE_UNAVAILABLE — Transaction state is pinned to the node that opened it. If that node crashes or becomes unreachable while the transaction is in progress, subsequent requests using the transaction token are rejected with this error because the proxy cannot forward them to the owner.

Raw formats

Section titled “Raw formats”