Buildbarn worker not receiving actions
The worker may be healthy but ineligible for queued work, connected to the wrong scheduler, or assigned to a platform queue with no matching demand.
Common causes
- Worker platform properties do not match queued actions
- Worker and clients use different schedulers or instance names
- Size-class configuration prevents assignment
- The worker lost registration or is failing health checks
What to check
- Confirm registration and scheduler endpoint
- Compare the routed action platform with the worker platform and configured action router
- Inspect queue demand by platform and size class
- Check worker logs around synchronization and operation assignment
Primary sources
Use these references to confirm protocol and version-specific behavior.
Investigate with build-level evidence
Hermetiq correlates Bazel actions, cache behavior, Buildbarn infrastructure, and remote-execution timing so teams can move from a status code to the build and system behavior behind it.
Technical review: July 20, 2026 · Verify flags and behavior against the Bazel and Buildbarn versions deployed in your environment.