Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Support BYHOUR in automation RRULE schedules

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…

Please allow Codex automation schedules to accept BYHOUR in RRULE definitions.

Root Cause

Please allow Codex automation schedules to accept BYHOUR in RRULE definitions.

Code Example

FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR;BYHOUR=9;BYMINUTE=0
RAW_BUFFERClick to expand / collapse

Summary

Please allow Codex automation schedules to accept BYHOUR in RRULE definitions.

Motivation

Automation scheduling currently supports recurring schedules, but RRULEs that include BYHOUR appear to be rejected. This makes it harder to express common schedules directly, especially when users want a recurring task at a specific hour without relying on a more limited schedule shape.

Example

A schedule like this should be accepted:

FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR;BYHOUR=9;BYMINUTE=0

Expected behavior

Codex automations should parse and accept valid RRULE schedules that include BYHOUR, and run the automation at the specified hour according to the user's configured timezone.

Actual behavior

Schedules containing BYHOUR are currently not accepted.

Use case

This would make automation scheduling more expressive and closer to standard RRULE semantics, allowing users to define precise hourly constraints for weekly or daily recurring automations.

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…

FAQ

Expected behavior

Codex automations should parse and accept valid RRULE schedules that include BYHOUR, and run the automation at the specified hour according to the user's configured timezone.

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 Support BYHOUR in automation RRULE schedules