Troubleshooting
Collect the right evidence before changing a transaction route.
Start with the network, timestamps and original submission outcome. Distinguish a connection problem from an on-chain execution outcome and a revenue reconciliation question.
Connection or authentication failure
Check the address, environment and credential scope against the information supplied for your integration. Capture the exact error and response time without exposing credentials. If the failure persists, contact your agreed technical owner before changing the route.
Submission timed out
A timeout does not establish whether the transaction was received. Reconcile the original submission using the agreed status mechanism and chain data. Apply the retry policy specified during onboarding; do not assume repeated submissions are idempotent.
Transaction remains pending
Check the chain outcome, account nonce and any application-side replacement or parallel submission. Record how long the transaction has been pending and the timing expectation agreed for the integration.
Confirm replacement or cancellation support before attempting either operation. A public reroute can change the transaction’s privacy.
Included transaction, no revenue
Successful execution and captured MEV revenue are separate outcomes. The flow may contain no viable opportunity. Review attribution and the agreed accounting period before treating an absent payment as an error.
Revenue discrepancy
Compare the same network, accounting period and agreed revenue basis. Check applicable costs and attribution records. Raise a reconciliation question with the supporting records rather than estimating revenue from the trade amount or gas fee.
Prepare a support brief
Network and environment:
First observed time (include timezone):
Transaction hash / correlation ID, if available:
Submission result or redacted error:
Observed on-chain outcome:
Expected outcome:
Recent routing or configuration changes:
Steps already taken:Use the contact agreed for your integration. For an initial discussion, book a call with the team ↗. Do not share private keys, seed phrases or authentication secrets.