getSendTransactionStatus
Chain-specific send detail, only when you need it.
Status
Proposed supporting compatibility behavior. It is one of the preserved original twelve descriptions, but is not a required repeated-status workflow and is not an available SDK.
Supporting action#
Read chain-specific detail for a send operation when an integration needs more than the business-level result returned by getOperation.
Proposed call#
getSendTransactionStatus(
input: GetSendTransactionStatusInput,
options?: CallOptions,
): Promise<SendTransactionStatus>
The TypeScript input uses sendTransactionStatusId; the result uses string-union states whose documented values serialize unchanged.
async def get_send_transaction_status(
input: GetSendTransactionStatusInput,
*,
options: CallOptions | None = None,
) -> SendTransactionStatus: ...
Python uses send_transaction_status_id and string-valued enum members. Task cancellation cancels only this read and cannot change or retry the transaction.
GetSendTransactionStatus(
ctx context.Context,
input *GetSendTransactionStatusInput,
) (*SendTransactionStatus, error)
Go uses SendTransactionStatusID with the stable send_transaction_status_id JSON name and a named string status type. Context cancellation has no transaction effect.
The input is the send-status identifier returned by a completed or progressing send operation. It is not a transaction hash.
Result#
Returns explicit submission, inclusion, execution and finality evidence only when the backend can distinguish them, plus safe failure detail. Missing hash before broadcast, nonterminal progress and unknown outcome remain distinct.
Effects and failures#
Read-only. It cannot submit, replace, cancel or retry a transaction. A failed read does not prove transaction failure. A transaction hash does not prove successful execution or finality. Callers that only need durable operation recovery use getOperation(requestId).
Acceptance#
- Positive: returned status is tied to the original send operation and preserves each known lifecycle boundary.
- Negative: no automatic resubmission occurs; unavailable does not become failed; included does not become final.
See sendTransaction and ethSendTransaction and getOperation.