Workflow schedules from an earlier configuration keep running after a redeploy #128

New Issue

2026-09-21T07:18:37Z

cgalo5758 commented

2026-09-21 07:18:37 +00:00

What happens

A schedule the console created under an earlier configuration stays registered once the configuration stops asking for it. Boot ensures the schedules the current configuration names and refreshes the arguments of one that already exists, but nothing removes one that is no longer wanted, so it keeps firing under its old name and its old arguments.

What should happen

After a boot, the schedules registered on the workflow service are exactly the ones the current configuration calls for.

Where

The schedule helpers in the workflow packages and the boot path that calls them.

Steps

Boot with a scheduled job enabled, change the configuration so that job is no longer wanted or is registered under a different name, boot again, and list the schedules: the old one is still there and still firing.

Why it matters

An orphaned schedule runs work the deployment has switched off, and its failures are reported against a deployment that no longer expects them. An operator has no way to tell from the console which schedules are current.

Migrated from status/issues.md at b7a0e15

## What happens A schedule the console created under an earlier configuration stays registered once the configuration stops asking for it. Boot ensures the schedules the current configuration names and refreshes the arguments of one that already exists, but nothing removes one that is no longer wanted, so it keeps firing under its old name and its old arguments. ## What should happen After a boot, the schedules registered on the workflow service are exactly the ones the current configuration calls for. ## Where The schedule helpers in the workflow packages and the boot path that calls them. ## Steps Boot with a scheduled job enabled, change the configuration so that job is no longer wanted or is registered under a different name, boot again, and list the schedules: the old one is still there and still firing. ## Why it matters An orphaned schedule runs work the deployment has switched off, and its failures are reported against a deployment that no longer expects them. An operator has no way to tell from the console which schedules are current. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

bug

area/ops labels 2026-09-21 07:18:37 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#128