›_ Codex Issues
Codex Issues / #16938

Automation marked Active but does not run or create a thread

Open 💬 2 comments Opened Apr 6, 2026 by janessanel
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary
On April 6, 2026, my automation did not run at its scheduled time. The automation is marked ACTIVE, but no new thread was created and no visible execution started. Note, that I have the Windows version of ChatGPT Codex that is available through the Microsoft Store

Automation details
Status: ACTIVE
Schedule: daily at 2:15 PM Eastern
Execution environment: worktree

Expected behavior
At 2:15 PM EDT on April 6, 2026, the automation should have:

  • started automatically
  • created a new thread
  • executed the prompt
  • produced visible run output

Actual behavior

  • no new thread appeared
  • no visible run output appeared
  • the automation remained marked ACTIVE
  • the scheduled run appears not to have started

Local evidence
Workspace shows:
status = "ACTIVE"
rrule = "RRULE:FREQ=WEEKLY;BYHOUR=14;BYMINUTE=15;BYDAY=SU,MO,TU,WE,TH,FR,SA"
Verified local time: 2026-04-06T16:11:15-04:00
.codex\logs_1.sqlite last write time: 2026-04-06T16:11:04-04:00
.codex\state_5.sqlite last write time: 2026-03-31T18:45:59-04:00
I could not identify a clear local trace of a run starting for this automation on April 6, 2026

Reproduction steps
Create or keep an automation active
Configure it to run on a daily schedule
Wait for the scheduled run time, or click Run now
Observe that no thread is created and no visible execution starts

Notes
This looks like the automation runner is failing before task execution begins. The issue does not appear to be specific to the automation prompt itself, since the symptom is that no thread or runnable task is created at all.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • ##15854
  • ##16936

Powered by Codex Action

quiezent · 1 month ago

Additional Windows/Codex Desktop reproduction, focused on schedule timezone evaluation:

  • Device timezone: Asia/Kuala_Lumpur (UTC+8); intended schedule timezone: America/New_York.
  • The automation was ACTIVE and stored an iCalendar DTSTART with TZID=America/New_York.
  • The Scheduled Tasks UI displayed “Custom schedule · Next run in 8 hours” at a time consistent with treating 09:30 as the Malaysia local clock, rather than 09:30 New York time.
  • The planned 11:00 ET checkpoint was missed: no scheduled automation wake/session was delivered to the target thread.
  • A manual “Run now” shortly afterward did deliver the saved prompt to the target thread, so the prompt and target-thread wiring itself were functional.

This may be the same runner defect as this issue rather than a separate timezone parser bug, but it suggests that DTSTART/TZID is not being honored by the desktop scheduler’s next-run calculation. Expected behavior: respect the IANA TZID, display the correct next run, and start the target-thread automation at the configured New York wall-clock time.

As a temporary workaround, I changed the schedule to Malaysia-time equivalents; that workaround needs a manual one-hour adjustment when U.S. daylight saving changes.