Rank, 14 days: 150 on the Codex sheet
3 people reported
All time, since Oct 20.
One-time automation reruns
“A one-time automation should not trigger again after its scheduled occurrence, even if the run fails or hits a usage limit.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/19971/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
One-time automations with COUNT=1 run again on later days. Saved rule FREQ=DAILY;COUNT=1 stayed ACTIVE, and the same automation delivered further unrequested runs after its scheduled occurrence.
Is this your bug?
File my report- Where
- Desktop automations
- Versions
- 26.1013.40934
- Platforms
- macOS, Windows
- How bad
- Breaks a normal workflow.
Not quite your bug?
Original reports4, newest first
- One-time Codex automation repeatedly ran on three consecutive days, consuming an estimated $10 in token usageOn the forum#1411490
- One-time Codex automation triggered on three consecutive days despite COUNT=1On GitHub#58616
- One-time Codex automation appears to have run again after completionOn GitHub#58455
- [macOS] One-shot heartbeat with COUNT=1 runs again the next dayOn GitHub#55576