TestProject Forum

The agent’s workers limit has reached [SOLVED]

Hi Team,

We have a couple of Jobs scheduled at non-overlapping time windows.
Recently we have upgraded our agent to the latest 3.1 and now we are getting the following issue when trying to run our job.

"The job failed to start due to the following reason:
The agent’s workers limit has reached. The execution is queued"

Once this issue occurs the pending jobs fail to execute.
We are not able to find any help on any forum regarding this issue…Can you please help ?

FYI found a way to restrict the max-number of workers. This can be done using CLI, just pass the parameter --max-workers with the start command.

E.g ./testproject-agent start --max-workers 1

getting the same problem - any solution?

Hi,
When agent reports job was queued because max workers has been reached, can you see it queued on the agents tab here?

And if you can see the queued job do they eventually start when the agent is idle?

Same issue here, and no they just sit in the queue when the agent is idle until you manually delete them. Is there a way to not have exceptions added to the queue?

Hi,
When the agent busy all jobs / test execution will be queued. we have an issue with queued jobs currently more info here:

I will reply here once the issue is resolved.

Hi,
The issue has been identified and resolved. 201 is now documented in our swagger at:
https://api.testproject.io/docs/v2/#/

Also queued jobs should immediately start when agent workers are available.

Let me know if there is any issue.