Stale cache results during Bamboo agent disconnect

Agent Configuration Synchronization

Atlassian Bamboo agents utilize a local cache of build plans and configurations to optimize execution. This system relies on a heartbeat mechanism and versioning checks to ensure the agent remains synchronized with the server's current state.

Cache Inconsistency Scenarios

When a disconnect occurs between the agent and the server, there is a risk that the agent may attempt to execute a build using an outdated plan configuration. This typically happens if a plan is updated on the server, but the agent fails to receive the update notification prior to the start of a build execution.

Given that cache clearing often requires a full restart of the agent process, the behavior of the versioning check during intermittent network latency is unclear.

• Does the agent automatically invalidate the local cache immediately upon detecting a heartbeat timeout?
• What is the expected behavior when a build is triggered while the agent is in a disconnected state but still possesses a local cached version of the plan?