Skip to content
Cyoda Documentation
Settings

TX_NO_STATE — no transaction state record found

cyoda-go version 0.8.3

errors.TX_NO_STATE

Section titled “errors.TX_NO_STATE”

NAME

Section titled “NAME”

TX_NO_STATE — no state record exists for the referenced transaction.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 404 Not Found. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

Reserved. Not currently emitted by any cyoda-go code path.

In the current model, transaction outcomes are tracked in-memory on the owning node for a bounded TTL window. There is no persistent two-phase-commit state log tracking prepare/commit/abort phases. A transaction that has expired from the in-memory window is reported as TRANSACTION_NOT_FOUND.

This error code is reserved for a future capability involving persistent per-transaction state records. If you receive it from a current cyoda-go release, it indicates an unexpected condition; raise a support ticket.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.TX_REQUIRED
  • errors.TX_COORDINATOR_NOT_CONFIGURED
  • errors.TRANSACTION_NOT_FOUND

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 TX_REQUIRED — Reserved. Not currently emitted by any cyoda-go code path.
  • cyoda help errors TX_COORDINATOR_NOT_CONFIGURED — Reserved. Not currently emitted by any cyoda-go code path.
  • 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.

Raw formats

Section titled “Raw formats”