Codex Scheduled Tasks execute at incorrect times and consume unintended usage

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

26.803.61601

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

I have a recurring Codex Scheduled Task configured with these recurrence rules:

RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR;BYHOUR=8,11,14,17,20;BYMINUTE=30

RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR;BYHOUR=10,13,16,19,22;BYMINUTE=0

The intended schedule is therefore:

08:30, 10:00, 11:30, 13:00, 14:30, 16:00, 17:30, 19:00, 20:30, 22:00

Monday through Friday.

My timezone is Asia/Baku (UTC+4).

On August 11, 2026 at approximately 13:22 local time, Codex showed “Next run in 40 minutes”, which corresponds to approximately 14:02.

However, 14:02 is not present in either configured RRULE. The correct next run should be 14:30.

This is not only a schedule display issue: the scheduled task actually executes at these incorrect times, causing unintended Codex usage / token consumption.

The UI also falls back to “Custom schedule…” for this task, while other scheduled tasks display their recurrence normally.

I have screenshots showing:

the current local time;
the incorrect “Next run” countdown;
the configured task;
previous executions.

Please investigate the scheduler / RRULE parsing issue.

What steps can reproduce the bug?

Feedback ID: no-active-thread-019ff02d-faa6-7051-98a9-07e5936c47ea

What is the expected behavior?

Additional information

No response

Start by locating the Codex App scheduler entry point and its RRULE parsing and next-run calculation tests; the issue names no files or tests. Reproduce the two weekly rules in Asia/Baku and verify that the displayed and actual next run is 14:30, with no execution at unintended times.