Timeout in outTx reporting usually cause missing outTx tracker hash

[ws4charlie]

Background:

Outbound tracker hash report easily get timeed out waiting for outTx receipt. This leads the problem of missing outbound tracker hash which blocks keysign scheduler processing more pending cctxs due to below error.
scheduleCctxEVM: nonce too high: signing 218758, earliest pending 218637

A quick remediation would be allowing zetaclient reporting outTx hash to tracker even if receipt is now available (e.g., due to gas price spikes).

Also, it's good to add chain id to the log print "scheduleCctxEVM: nonce too high: signing 218758, earliest pending 218637" so we know which chain is blocked.

[brewmaster012]

A quick remediation would be allowing zetaclient reporting outTx hash to tracker even if receipt is now available (e.g., due to gas price spikes).

you meant is not available?
We used to be like that right?

[ws4charlie]

@brewmaster012 we used to report any broadcasted outTx hashes without checking anything and that flooded the outTx tracker with 134 hashes. Now we wait for receipt before reporting the hash but it could take > 10 mins for the receipt to be available (e.g., gas price spikes).