Here is an article draft that is as follows:
Ethereum: Chainlink Job stuck into the submission task, despite successful transactions at Etherscan
Like a Chainlink Node user, I am sure that many have faced problems when our work is stuck with the submission task. I have recently experienced a frustrating situation when Chainlink’s work is stuck after you have successfully carried out a transaction at Etherscan.
Data from an API, processed, then a contract with the ETHTX task. The work was successfully completed, but I noticed that it was in the submission TX process.
Symptoms of the question
I began to notice that my work was stuck after about 10-15 minutes inactivity. The reason for this may be various reasons, for example:
- Network congestion or slow data request from API
- Inadequate gas prices for a call contract
- Incorrectly configured Chainlink node settings
How did I solve the problem
I went through step -by -step analysis. So I did:
- Double check the Etherscan transaction
:
Or
- Optimized Network Configuration : I modified my node network settings to optimize the gas prices of the contract call, ensuring that it does not stop due to high charges.
- Updated Chainlink Node Version
:
Tips to troubleshoot
Work, here are some additional tips to help you solve them:
- Make sure that the APIs are correct and within the authorized limits.
- Check the network configuration and optimize gas prices as needed.
Or
*
Following these steps, you should be able to solve the problem with the stuck work and return and run. If you have any additional questions or problems please ask!