[Bug]: When Bridging to Solana the activity incorrectly shows the tx incompleted

[davibroc]

Describe the bug

When bridging to any network to Solana, the first transaction works correctly. However, for the second transaction, the getTxStatus API call returns a 500 internal error while it's pending. Once the transaction is complete, it returns the status COMPLETED correctly, but the UI still shows the transaction as pending. See the video for more details.

Expected behavior

No response

Screenshots/Recordings

tx.never.complete.mov

Steps to reproduce

1. Select any network.
2. Bridge any token to Solana.
3. Monitor the network tab in the background worker.
4. Notice that getTxStatus initially returns a 500 error, and once the transaction is completed, the UI does not show the transaction as completed.

Error messages or log output

Detection stage

During release testing

Version

12.14.0

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

No response

[Unik0rnMaggie]

Reproduced for bridge from Avalanche network to Solana network:

[davibroc]

It also happens on the build without Solana when Bridging from Optimism

[ziedbrini]

@davibroc Hey, fyi, I added the team label. Is the bug still happening in the latest beta build? cc: @chaoticgoodpanda

[chaoticgoodpanda]

Hi, @GustavoRSSilva is working on this one. Related Jira ticket you can check comments for status: https://consensyssoftware.atlassian.net/browse/MMS-2026?atlOrigin=eyJpIjoiNmZlNmI4Y2MyZGRlNDQ1ZGJmNjE5YTBkZjRjNWI0NjIiLCJwIjoiaiJ9