feat: Trigger immutable runs with overlap policies #322

New issue

Closed

opened 2026-07-13 19:46:13 +02:00 by dries · 0 comments

dries commented

2026-07-13 19:46:13 +02:00

Owner

Parent

#311

What to build

Attach durable manual, interval, cron, PR, child-completion, and turn-completion triggers to active workflow versions. Every firing creates a separately auditable run, with explicit behavior when a previous run is still active.

Acceptance criteria

Trigger configuration is validated and versioned with the workflow definition.
Each firing snapshots trigger details and creates a run pinned to the active workflow version.
Overlap supports skip, queue, and parallel; skip is the default.
Queued firings survive restart and start in deterministic order when capacity becomes available.
Interval/cron triggers reuse existing timing behavior and avoid backfiring arbitrary historical slots.
PR triggers reuse existing forge detection/auth and persist stable event detection state.
Child/turn completion triggers reuse platform status inference and do not double-fire one event edge.
Trigger state, next check, last firing, overlap decision, and resulting runs are visible in the UI.
Tests use fake clock, forge, and session-status seams to cover all trigger and overlap modes.

Blocked by

#313

## Parent #311 ## What to build Attach durable manual, interval, cron, PR, child-completion, and turn-completion triggers to active workflow versions. Every firing creates a separately auditable run, with explicit behavior when a previous run is still active. ## Acceptance criteria - [ ] Trigger configuration is validated and versioned with the workflow definition. - [ ] Each firing snapshots trigger details and creates a run pinned to the active workflow version. - [ ] Overlap supports skip, queue, and parallel; skip is the default. - [ ] Queued firings survive restart and start in deterministic order when capacity becomes available. - [ ] Interval/cron triggers reuse existing timing behavior and avoid backfiring arbitrary historical slots. - [ ] PR triggers reuse existing forge detection/auth and persist stable event detection state. - [ ] Child/turn completion triggers reuse platform status inference and do not double-fire one event edge. - [ ] Trigger state, next check, last firing, overlap decision, and resulting runs are visible in the UI. - [ ] Tests use fake clock, forge, and session-status seams to cover all trigger and overlap modes. ## Blocked by - #313