Project/Runbook Triggers That Have Been Disabled Fire Unexpectedly When Re-Enabled

[briggs-octo]

Severity

1 customer report

Version

2025.4.10306, 2026.1.3124

Latest Version

None

What happened?

Runbook triggers that are disabled fire unexpectedly when re-enabled.

Reproduction

1. Set up a Runbook with a published snapshot.
2. Configure a Runbook Trigger for the runbook set up in step 1, using a Runs Daily schedule with the trigger time set to 1-2 minutes in the future.
3. Disable the trigger.
4. Wait for the trigger time to pass, and then re-enable the trigger.
5. See that a Runbook Run is kicked off for the underlying Runbook based on the trigger being re-enabled.

Error and Stacktrace

More Information

No response

Workaround

Change the time on the trigger first, save the change, and then re-enable the trigger.

[octoreleasebot]

Release Note: Fix project triggers running unexpectedly when re-enabling

[pumacln]

Thanks for the quick turnaround

[Octobob]

🎉 The fix for this issue has been released in:

Release stream	Release
2025.4	2025.4.10331
2026.1	2026.1.4488
2026.2+	all releases