Deleting a worker is undone by its next heartbeat #34

New Issue

2026-09-08T20:57:34-04:00

jared commented

2026-09-08 20:57:34 -04:00

Overview

Admin Delete on the Workers tab removes the row, but the worker's next heartbeat (every 30 s) re-inserts it with a new id, so the worker reappears within a minute – and any scheduled command that referenced the old id now points at nothing. The button gives no indication of this.

Suggested fix

Either restrict Delete to offline workers (and say so), or add a decommissioned flag that rejects further heartbeats until re-enabled. Warn when a deleted worker is referenced by schedules.

## Overview Admin **Delete** on the Workers tab removes the row, but the worker's next heartbeat (every 30 s) re-inserts it with a new id, so the worker reappears within a minute – and any scheduled command that referenced the old id now points at nothing. The button gives no indication of this. ## Suggested fix Either restrict Delete to offline workers (and say so), or add a `decommissioned` flag that rejects further heartbeats until re-enabled. Warn when a deleted worker is referenced by schedules.

jared added the bug ux frontend backend priority/low labels 2026-09-08 20:57:34 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: LotusGuild/pulse#34