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
minted ERC20 (note: the https://ethlance.qa.district0x.io/dev/contract-ops amount entry for ERC20 needs to be 100x greater than the amount you want, to account for the 2 decimal places that the TEST uses)
created a job
Tx was mined successfully (UI logged it in development console) but back-end doesn't have the information
I think the solution could be to add a health-check endpoint - e.g. if an event comes in (detected by syncer) but doesn't get processed, then the service can mark it as being in bad state and I can then investigate and/or restart it.
Additionally, to reduce the possible points that can fail, I could extract the syncer part out and start it as a separate process. But it's not very clear (due to lacking evidence of what's causing the issue) if it would help.
I minted ERC20 here: https://sepolia.arbiscan.io/tx/0x2680a0d912c390be86064bfea907d7e32b9c965060edb6c11b53b5b6221c7d91
I get failing tx:
The text was updated successfully, but these errors were encountered: