gnosis / gnosis/safe-cmm-app-react
Bug: Transaction stuck on pending
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
# Description
A user reports there's a pending tx stuck on his Safe.
User is also not able to deploy new strategies. Possibly related.
# To Reproduce:
Not able to reproduce
# Reported user steps
1. User deployed a strategy
2. Transaction was stuck on metamask, so the user cancelled it
3. Transaction still shows as pending on his Safe, even after reloading, different browser and so on
4. User reports they did not succeed to deploy new strategies since then
# Expected Behaviour
There are no pending txs after cancelling them and new txs can be deployed without issues
# Actual Behaviour
Even after cancelling the Metamask transaction, CMM pending tx is still present.
We can see that by checking the response of https://safe-transaction.xdai.gnosis.io/api/v1/safes/0x45323abC6e9FCf87654001B893EA4f41bb4a8190/transactions/?nonce__gte=6&executed=false
Also, user is not able to deploy a new strategy.
When we look at the console errors though, there's an error when loading the txs (see screen shot on next section).
Still, the tx that fails is one that has been executed, not the pending one:
Failed tx: [0xe4ae065861f9a501781f14a1ed0949290328cdea989ec29081e421fe916ce2a0](https://dashboard.tenderly.co/tx/xdai/0xe4ae065861f9a501781f14a1ed0949290328cdea989ec29081e421fe916ce2a0)
User's Safe has no pending CMM tx to be signed.
The Safe has a single owner, thus it shouldn't have any pending tx anyway.
# Screenshots/Videos
## Pending tx

## Safe txs page

## Deploy page error

## Error logs


# Environment
**Desktop:**
- OS: [e.g. iOS]
- Browser Chrome
- Version 0.4.6
# Background
N/A
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the transaction-loading path used by the Safe transactions endpoint and the deploy page. Compare the pending transaction response with the reported executed transaction and inspect the console errors shown in the issue. Done means cancelled transactions no longer remain pending and new strategies can be deployed successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100