You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We have been using biconomy for months to develop a dApp.
Today issuing transactions stopped working.
The transaction still goes through to the mempool on polygon mumbai,
but it gets stuck there with the message:
Pending This txn hash was found in our secondary node and should be picked up by our indexer in a short while.
After a few minutes, the hash is gone from polygonscan.
Expected behavior
Transaction should be mined and confirmed.
Mexa SDK version (please complete the following information):
Version: [e.g. 2.0.38]
Additional context
It seems like using a higher gasPrice could solve the issue.
But how can we set the gas manually when issuing a transaction through biconomy/mexa?
The text was updated successfully, but these errors were encountered:
Describe the bug
We have been using biconomy for months to develop a dApp.
Today issuing transactions stopped working.
The transaction still goes through to the mempool on polygon mumbai,
but it gets stuck there with the message:
Pending This txn hash was found in our secondary node and should be picked up by our indexer in a short while.
After a few minutes, the hash is gone from polygonscan.
Expected behavior
Transaction should be mined and confirmed.
Mexa SDK version (please complete the following information):
Additional context
It seems like using a higher gasPrice could solve the issue.
But how can we set the gas manually when issuing a transaction through biconomy/mexa?
The text was updated successfully, but these errors were encountered: