### 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. <img width="1280" height="898" alt="Image" src="https://github.com/user-attachments/assets/15dfd007-00a4-4cc2-9142-ad1358eec9a2" /> I waited for final_execution_status to be EXECUTED and still tx.status is the same "Started". <img width="1280" height="526" alt="Image" src="https://github.com/user-attachments/assets/ddf7d375-47cd-41ee-8d0d-5c06289efa28" /> ### Is it an archival request? - [ ] The result contains archival data