A job stays queued
Check whether its lane was routed to Darkbloom. A lane that was routed cannot fall back any more: if Darkbloom then refuses its jobs (a balance too low to hold, a revoked link or consent, a cap reached meanwhile, or repeated infrastructure failures), they stay queued on GitHub. Cancel the run and re-run it, which routes again. With the watchdog workflow that happens by itself after the configured wait. A job can also wait queued because it is at your concurrency or resource limit. The watchdog cannot tell that wait from a fault: raiseDARKBLOOM_WATCHDOG_MINUTES above it.
A lane fell back
The route job’s summary gives the reason. The reasons and what to do:
The route workflow itself can also keep every lane on its fallback:
A job fails on a Darkbloom runner
- It uses a secret, an environment, services, a container or a container action. Those jobs are refused and stay queued. Move secrets to environments and keep such jobs on your own runners.
- Its permissions are missing or
read-all. A routed job needs explicitreadornonepermissions on the job or the workflow. - It calls a reusable workflow from another repository. Darkbloom cannot verify it, so every routed job of that workflow is refused. Copy the route workflow locally and keep the job’s workflow free of remote reusable workflows.
- It downloads from an unapproved host. The step fails. Ask your Darkbloom contact to add the host; see caching and network.
- A tool is missing or a version differs. Check
runner images. Linux jobs cannot
apt install; install into the scratch disk or use an action. - A cache misses. A job on another Mac misses Darkbloom’s build cache, and pull requests from forks get none. GitHub’s caches behave as usual.
- The Mac dropped off the network. GitHub fails the job. If Darkbloom operates your approval’s watchdog for that lane, it re-runs the job once, after the run completes.
- It publishes, releases or deploys. Keep those jobs on your own runners, and keep the jobs that save caches releases restore there too.
Pull requests from forks
The route workflow keeps them on their fallback runners without asking Darkbloom. Nothing is wrong.Darkbloom is down
Lanes fall back before any job is queued, so new runs use your runners. Jobs already routed wait for Darkbloom; if it refuses them they stay queued, and you cancel and re-run. The watchdog workflow does that after its wait.The approval expired
Lanes fall back until it is renewed: choose Request renewal in the console. A denied request says the operator’s reason; fix it and choose Request again.Stop using Darkbloom
Set the repository variableDARKBLOOM_ROUTING to anything but on, or remove
the route job. Disconnect the installation in the console to stop paying
for it, and uninstall the App on GitHub to remove its access.
