A similar thing happens to us from time to time. A job running on the remote agent just starts throwing an error in the middle of the run. There is no error description or anything. When the job is ‘done’, the agent is still marked as busy and it won’t run the next scheduled job. It will just queue the jobs. The agent has to be manually restarted to get to the idle state. Using version 3.3.0 (but happened before), running headless Chrome on Windows. Any advice? Thanks
If your agent reached max workers the message stated is correct and it’s not an error.
If the agent is busy working on a different execution or the worker is still finalizing or uploading the report of the latest execution, the message Job failed to start due to “The agent’s workers limit has reached. The execution is queued” is completely by design.
If you are experiencing a different issue where the agent shows 0/1 workers on the UI but the execution still does not start, or you are experiencing an issue when execution is getting stuck and the agent keeps reporting 1/1. (has been resolved)
Please contact us on any of our support channels.
These are different issues and are not related to the message which correctly states that the execution was queued.
If you believe you get the message wrongly without a proper reason, please contact us with the agent logs and screenshots that will help us get a better understanding of the issue.