Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLIPublic
Assigneesstack72

Relationships

#1659 serve reload should pick up trigger override changes from serve.yaml

Opened by stack72 · 8/14/2026· Shipped 8/14/2026

Context

Follow-up to #1644 (trigger override CLI commands) and #2148.

swamp workflow trigger set/get/remove commands write trigger overrides to .swamp/serve.yaml. However, the running swamp serve instance only reads trigger overrides once at startup — swamp serve reload (SIGHUP / WebSocket serve.reload) reloads extension bundles and the trust list, but does not re-read the triggers section from serve.yaml.

This means after swamp workflow trigger set --server, the user must restart serve for the new schedule to take effect.

Proposal

Extend serve reload to also re-read trigger overrides from serve.yaml and apply them to the running ScheduledExecutionService.

Implementation sketch

  1. Add an updateTriggerOverrides(overrides: ReadonlyMap<string, TriggerOverride>) method to ScheduledExecutionService that diffs against the current overrides and calls handleScheduleChange for additions/changes and unregister for removals
  2. Thread the ScheduledExecutionService instance into performServeReload (or add a separate callback)
  3. In performServeReload, call loadServeConfig to re-read serve.yaml and pass the new trigger overrides to the service

Considerations

  • The triggerOverrides field on ScheduledExecutionDeps is currently ReadonlyMap — the update method would mutate internal state, so the deps field stays readonly but the service gains a setter
  • handleScheduleChange already consults the override map and handles register/unregister correctly — the watcher path exercises this for workflow YAML changes, so the pattern is proven
  • The applyTriggerOverrides startup method handles adding schedules to unscheduled workflows — the update method needs the same logic for newly-added overrides
02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 4 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

8/14/2026, 11:49:05 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack728/14/2026, 10:35:45 PM

Sign in to post a ripple.