Sometimes after a transaction regarding the deployment of a new Task is confirmed the cron job yields an exception:
UnhandledPromiseRejectionWarning: Error: Couldn't decode uint256 from ABI: 0x
This only occurs on the Mainnet. Reason could be that the transaction receipt doesn't return the final contract address but "0x" instead.
Since this is a Mainnet-only bug, it's very hard to fix it since deploying a single task costs around ~1$ currently (24.08.18).
Sometimes after a transaction regarding the deployment of a new Task is confirmed the cron job yields an exception:
UnhandledPromiseRejectionWarning: Error: Couldn't decode uint256 from ABI: 0xThis only occurs on the Mainnet. Reason could be that the transaction receipt doesn't return the final contract address but "0x" instead.
Since this is a Mainnet-only bug, it's very hard to fix it since deploying a single task costs around ~1$ currently (24.08.18).