Weekly automation RRULE ignores additional BYHOUR values

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.325.31654 (1272)

What subscription do you have?

enterprise

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

Summary

Codex automations appear to ignore additional BYHOUR values when using a weekly RRULE.

A rule intended to run multiple times per weekday:

FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR;BYHOUR=8,12,16;BYMINUTE=0

was scheduled as if only the first hour (8) mattered.

Expected behavior

Given the current local time:

• 2026-04-01 09:46 CEST

the next run for this RRULE should be:

• 2026-04-01 12:00 CEST

because 12:00 and 16:00 are still upcoming today.

Actual behavior

The automation UI reported the next run as:

• 2026-04-02 08:00 CEST

The persisted automation state also stored next_run_at for tomorrow morning rather than today at noon.

Environment

• Codex desktop app
• Local timezone: Europe/Prague
• Observed at: 2026-04-01 09:46 CEST

Notes

As a workaround, I had to split the automation into three separate weekday automations:

• BYHOUR=8
• BYHOUR=12
• BYHOUR=16

This suggests either:

• multi-value BYHOUR is not supported for weekly rules, or
• it is intended to be supported but the scheduler/UI computes next_run_at incorrectly.

What steps can reproduce the bug?

1. Create or edit an automation.
2. Set the schedule to:

FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR;BYHOUR=8,12,16;BYMINUTE=0

1. Check the “next run” value during a matching weekday after the first scheduled hour but before later scheduled hours.
2. Observe that the next run is calculated as the next day’s first slot instead of a later slot on the same day.

What is the expected behavior?

Given the current local time:

• 2026-04-01 09:46 CEST

the next run for this RRULE should be:

• 2026-04-01 12:00 CEST

Additional information

_No response_