Skip to content

RPC Issue: tx.status == 'Started' when final_execution_status == 'EXECUTED' #13872

@mattlockyer

Description

@mattlockyer

Contact Details

matt@proximity.dev

Which network are you using?

testnet

RPC URL

https://test.rpc.fastnear.com

RPC Request

functionCall

Expected result

tx.status == the final tx SuccessValue e.g. tx.status.Successvalue = '' or base64 return value

This is what all the tooling currently expects.

Actual result

tx.status == 'Started'

More context:

Using Near JS Packages 0.2.1 (same as before the last testnet upgrade), the following behavior manifested.

RPC is showing tx.status = "Started" when final_execution_status is EXECUTED_OPTIMISTIC.

Image

I waited for final_execution_status to be EXECUTED and still tx.status is the same "Started".

Image

Is it an archival request?

  • The result contains archival data

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions