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
If transaction fails, then fields like actualGasCost and actualGasUsed should not be recorded in db, as they refer to the information recieved from UserOperationEvent which was not emitted in this transaction. Check the tx on explorer
The text was updated successfully, but these errors were encountered:
I remember this bug now, it was saving the data incorrectly. The lastest entry of this is of a transaction from Jan 2024. Since then we have processed a lot of transactions and no transaction has this issue. It is safe to assume that this won't happen again.
Cluster : biconomy-sdk-prod
Database: relayer-node-service
Collection: useroperations_137
Inconsistency 1
Query Used in Mongo Shell
db.useroperations_137.count({status: "FAILED", success: "true"})
Results
Expected Outcome
There should not be any records where status is FAILED but success field is marked true.
Inconsistency 2
If a blockchain transaction fails, then there should not be any actualGasCost and actualGasUsed fields in the useroperations_ collection.
Query Used in Mongo Atlas UI
{transactionId: '0x7a7476d2451b17c81de9866efe6aa44a4124ba67ff4062a02718e9b825470074'}
Results
Expected Outcome
If transaction fails, then fields like
actualGasCost
andactualGasUsed
should not be recorded in db, as they refer to the information recieved from UserOperationEvent which was not emitted in this transaction.Check the tx on explorer
The text was updated successfully, but these errors were encountered: