Bamboo build queue status is not seen in Build Activity dashboard

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible


Sometimes builds do not show up under the Queue section inside the Build > Build activity page. The builds only start showing up on the page once the build starts (under the Building section).


Issue was seen in 8.0.4 but it can be applicable for other Bamboo versions as well.


It is important to identify if all builds are in queued state and not seen in the build dashboard or just one. To understand if the build was queued immediately after it got dispatched, then it means that Bamboo did not spend too much time updating the repository cache. It should've appeared in the queue. 

2021-11-30 11:10:37,991 INFO [7-DelayedChangeDetectionThread:pool-13-thread-5891] [ChainExecutionManagerImpl] Build NWP-JOB1-1 has been dispatched
2021-11-30 11:10:37,992 INFO [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-6] [BuildQueueManagerImpl] Attempting to queue Git LFS - gitlfs testing - Default Job #37 (NWP-JOB1-1).
2021-11-30 11:10:37,993 INFO [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-6] [ExecutionPhaseServiceImpl] Git LFS - gitlfs testing - Default Job #1 (NWP-JOB1-1) queued
2021-11-30 11:10:38,000 INFO [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-8] [BitbucketServerBuildStatusUpdater] Sending build notification to Stash (build key: NWP-JOB1-1, repository: new-repo)
2021-11-30 11:10:38,007 INFO [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-6] [BuildQueueManagerImpl] Sent ExecutableQueueUpdate: addToQueue, agents known to be affected: []

Along with the above message, if you see Bamboo reporting several errors attempting to access files inside the <BAMBOO-HOME>/shared/serverState/queue folder with the following stack:

2021-11-30 11:12:06,253 INFO [http-nio-8085-exec-55] [CommonContextMaps] Loading common context for GWP-JOB1-19
2021-11-30 11:12:06,253 INFO [http-nio-8085-exec-55] [XStreamQueuePersisterImpl] Loading offloaded context for: GWP-JOB1-19
2021-11-30 11:12:06,254 ERROR [http-nio-8085-exec-55] [JsonStreamResult]
java.lang.RuntimeException: Unexpected exception
        at com.atlassian.bamboo.util.BambooObjectUtils.asRuntimeException(
        at com.atlassian.bamboo.struts.JsonStreamResult.execute(
        at com.opensymphony.xwork2.DefaultActionInvocation.executeResult(
        at com.opensymphony.xwork2.DefaultActionInvocation.invoke(
        at com.opensymphony.xwork2.interceptor.DefaultWorkflowInterceptor.doIntercept(
        at com.atlassian.bamboo.ww2.interceptors.BambooWorkflowInterceptor.validateWorkflow(
        at com.atlassian.bamboo.ww2.interceptors.BambooWorkflowInterceptor.doIntercept(
        at com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(
        at com.opensymphony.xwork2.DefaultActionInvocation.invoke(
        at com.opensymphony.xwork2.validator.ValidationInterceptor.doIntercept(
        at com.atlassian.bamboo.ww2.interceptors.BambooValidationInterceptor.validate(
        at com.atlassian.bamboo.ww2.interceptors.BambooValidationInterceptor.doIntercept(
        at com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(
        at com.opensymphony.xwork2.DefaultActionInvocation.invoke(
        at com.atlassian.bamboo.ww2.interceptors.FieldErrorUsageVerifier.intercept(
Caused by: /var/atlassian/application-data/bamboo/shared/serverState/queue/GWP-JOB1-19 (No such file or directory)
        at Method)
        ... 277 more


It is important to understand here that generally, this issue appears when the builds are actually waiting for the change detection to happen and it is being loaded in the cache. If there are many builds which are referring to the same repositories then it this quite possible that you may encounter this issue. 


Restarting Bamboo could help resolve this issue.

Last modified on May 11, 2023

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.