I have an autotask running for several days. But In the last few, the same autotask has being failing from time to time. Giving timeouts.
It works 4 out of 5 times in average.
Hey @SandmanFinance! This could be caused by a slow network provider in our backend. Do you mind sharing your Autotask ID, so we can pinpoint the culprit? You can get it from the URL.
This is the ID: 5d262dd3-2150-471a-ba6b-55fd3ad28ea4 of the picture.
But also we had issues on this: b21f1322-5db7-4ffe-a9d9-f5ca42252098, e426ffee-6145-40bb-914b-899c2c937a25
Hey @SandmanFinance! We've removed some faulty/slow RPC providers for Polygon from Defender two days ago, which should have reduced the number of timeouts. Can you confirm if you're still experiencing timeouts in your Autotask?
About this: the relayer API returns a success when the transaction is sent, but it doesn't wait for it to be mined, since that could take several minutes (if not more, on low gas prices). It then keeps monitoring the tx (and resubmitting as needed) to make sure it gets mined. In the case you linked, the tx was successfully mined, but it reverted. Given it was an out-of-gas error, I'd suggest you pad your txs with some extra gas limit to prevent these issues.
The above is just an example. Make sure to check what gas limit you need for your specific use case. You can also run an estimateGas to get an approximation, and then add an extra on top of that to be safe.