-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting intermittent "most likely to fail" warning when executing batch (USDC transfer) transaction [ETH network] #269
Comments
Hi team, reporting another user with the same issue. Getting the same error above and wallet does not pop up for confirmation when doing batch transaction with USDC token. Please see video recording, |
Hey team, just got an update from the user. They've noticed an inconsistency in the issue, indicating a problem with the Safe backend. They spent a whole day refreshing the page dozens of times. Out of all those tries, only 2-3 actually worked. They ended up successfully executing the batch transaction. |
Hello team, we're still getting complaints on this issue from the same and other users. Is this more of a browser issue? Or safe issue? |
The only workaround right now is to repeatedly refresh; occasionally, it might work. |
checking the status with the team |
Please, follow the ticket safe-global/safe-client-gateway#750 |
Thank you Liliya. Closing this. |
Issue Category
Transaction execution issue
What happened?
User is trying to send USDC in a batch but getting an intermittent "most likely to fail" warning when executing. Was able to execute batch using another browser and then when trying to execute another batch, it gives the same error again:
https://app.safe.global/transactions/queue?safe=eth:0x24901F1b9b41e853778107CD737cC426b456fC95
Date and time this happened or you first noticed this issue
14-08-2023
Network
Ethereum Mainnet
Safe Address
0x24901F1b9b41e853778107CD737cC426b456fC95
Token Address
No response
Token Type
None
Transactions
No response
The text was updated successfully, but these errors were encountered: