Offline runner cleanup

The Offline runner cleanup panel sits on Overview for users with manage permission. It removes runners that stay OFFLINE (no heartbeat) longer than a retention period so crashed CI agents and replaced VMs do not clutter inventory.

▥

Offline runner cleanup (Overview)

This panel lets you configure automatic cleanup and shows a preview of runners that will be removed on the next cleanup run.

Enable automatic cleanup

Automatically remove runners that have been offline for a specified number of days.

Days offline before removal

30 ↕

days (1 – 365)

Runners offline for more than this number of days will be removed.

i Runners with active jobs are never removed, even if they look offline.

⌕

Next cleanup preview

12 runners will be removed on the next cleanup run (these runners have been offline for more than 30 days).

Runner name	Offline since
ci-runner-1	2026-07-10 (45 days)
dev-runner-2	2026-07-08 (47 days)
k8s-runner-3	2026-06-28 (57 days)
win-runner-4	2026-06-20 (65 days)
test-runner-5	2026-06-18 (67 days)

⚙

Policy

Configure when offline runners should be automatically removed.

Setting	Range	Default
Enable automatic cleanup	on / off	off
Days offline before removal	1 – 365	30

i Runners with active jobs are never removed, even if they look offline.

! When auto-cleanup is on, the panel previews how many runners the next job would delete and lists their names.

▥

Manual remove

Remove offline runners immediately without waiting for the scheduled cleanup job.

Filter or select

Filter Overview to Offline, or select specific offline rows.

Status

Offline ⌄

→

Click remove

Click Remove offline runners (N).

▥ Remove offline runners (N)

→

Confirm

Confirm the removal in the dialog.

Remove 5 offline runners?

→

Re-register

Agents must re-register with a new command to reconnect.

$ axioctl runner register

 --name my-runner

i Online or non-offline selections are skipped. Disconnect from the row menu is the same delete for a single runner.

Offline runner cleanup