codex - 💡(How to fix) Fix Desktop automation UI shows recurring interval for one-shot heartbeat (COUNT=1) [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19094Fetched 2026-04-24 06:01:06
View on GitHub
Comments
2
Participants
2
Timeline
4
Reactions
0
Timeline (top)
commented ×2labeled ×2
RAW_BUFFERClick to expand / collapse

What happened?

When I create or update a thread heartbeat automation with a one-shot RRULE (FREQ=MINUTELY;INTERVAL=20;COUNT=1), the automation card in the Codex desktop app still displays the interval as recurring ("Every 20 min").

The saved automation TOML correctly contains COUNT=1, so this looks like a UI interpretation/display bug.

Repro steps

  1. Create a heartbeat automation in a thread.
  2. Update it to one-shot RRULE: FREQ=MINUTELY;INTERVAL=20;COUNT=1.
  3. Open the automation card/details in the app.

Expected

UI should indicate this is a one-time run (or at least not show it as recurring forever).

Actual

UI shows recurring interval ("Every 20 min") even though RRULE has COUNT=1.

Extra context

  • Automation file contains: rrule = "FREQ=MINUTELY;INTERVAL=20;COUNT=1"
  • This creates operator confusion and risk of unnecessary worry about repeated runs.

extent analysis

TL;DR

The issue can be resolved by updating the UI interpretation of the RRULE to correctly handle the COUNT=1 parameter and display one-shot automations as non-recurring.

Guidance

  • Verify that the automation TOML file indeed contains the correct COUNT=1 parameter to confirm the issue is UI-related.
  • Check if the UI code has a specific handling for COUNT=1 in RRULE, and if it's correctly implemented to display one-shot automations.
  • Consider adding a conditional statement in the UI code to check for COUNT=1 and display a "one-time run" or similar indicator instead of the recurring interval.
  • Review the UI documentation to ensure it accurately reflects the expected behavior for one-shot automations.

Example

rrule = "FREQ=MINUTELY;INTERVAL=20;COUNT=1"

This TOML configuration should be correctly interpreted by the UI as a one-shot automation.

Notes

The issue seems to be specific to the UI interpretation of the RRULE, and the fix should focus on updating the UI code to correctly handle the COUNT=1 parameter.

Recommendation

Apply a workaround by updating the UI code to correctly handle the COUNT=1 parameter, as the issue is likely due to a UI interpretation bug rather than a fundamental problem with the automation configuration.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Desktop automation UI shows recurring interval for one-shot heartbeat (COUNT=1) [2 comments, 2 participants]