When agents are restarted:Build jobs(which are queued while the agent is offline) not picked up by agent even if the agent is in the Idle state and eligible for executing the build.

Issue Summary

When agents are restarted or got stopped and came back online after the restart, build jobs which are in the queued state while the agent is offline are not picked up by the agent when it comes back online.

The build job stays in the queue indefinitely and the job is marked as "No agent can build this job.".

When queueing the job again(with a new build) the job is picked up and executed by the same agent correctly.

This is observed in both remote and local agents.

This is reproducible on Data Center: (yes)

Steps to Reproduce

1. Create a Plan with a simple script job.
2. Create one local agent or remote agent.
3. Stop the agent from the respective agent page > Request Stop agent option. or you can stop the agent manually from the agent server.
4. Start a build for the plan now.
5. It will be in the queued state under the build activity page.
6. Now restart the agent from the agent page > Restart option or start the agent manually.
7. The agent will not pick up the job from the queue.
8. If you start a new build run for the same job it will be processed and executed by the same agent.

Expected Results

• Bamboo will process the pending jobs from the queue and assign Online eligible agents to execute the build.

Actual Results

• Bamboo is not processing the pending build jobs from the queue and the job stays indefinitely in the queued state until the build is stopped is manually.

Workaround

• Workaround is to Stop and rerun the job, Bamboo will process the job and assign an agent to it.