Successful Tx flagged as failed?

[twblack88]

Overview

This one is a bit strange. I had some ETH and went to send a test amount of like $100 or so. Went through the send flow and signed the Tx in my MM connected to the app.

Tx succeeded on chain, but

• on the activity tab it showed as failed
• it triggered the success toast but didn't sit as pending on the drawer

Ideally we make small amount sending more seamless and safe.

References and additional details

Tx from etherscan was fine

But on the activity tab it got flagged as failed.

Acceptance Criteria

• We tighten up the pipeline from send -> drawer -> activity. making sure we have tx's properly flag
• investigate why this guy got flagged as failed on our transactions. 0x9f589048633134cb89753a72e92ed8a5d53f26aea9be27e8e3d68d6e86fc451f

Need By Date

No response

Screenshots/Mockups

No response

Estimated effort

No response

[0xean]

networking request failing creates incorrect state for the transaction itself.

[0xean]

@shapeshift/operations can you help us to determine if you are able to replicate this? If its able to replicated, engineers can pick it up, but otherwise might close it without more information / reports of this.

[purelycrickets]

Ops is currently unable to recreate the 'failed' error message state of this issue:

@twblack88 were you ever able to reproduce this issue consistently, or was this a one off? I am in support of closing this issue if we cannot reproduce the error.

[twblack88]

One off. @purelycrickets closing 🤝