Codex App automations can disappear or show daily schedules as weekly-all-days
Open 💬 2 comments Opened Jun 10, 2026 by kotodamaP
Summary
I observed two automation-related issues in Codex App:
- Existing recurring automations disappeared from the "Current" automation list.
- A daily automation appeared to be represented as a weekly RRULE with every day selected.
No private paths, prompts, database contents, account details, or environment-specific configuration are included here.
Observed behavior
- Active automations appeared missing from the Codex App UI.
- The automations were not intentionally deleted.
- Local repair showed that TOML/registry drift could make the UI stop showing them.
- A daily schedule may be stored or displayed as a weekly schedule with all weekdays selected, which is confusing and may look like the cadence changed from daily to weekly.
- The UI did not show a clear error for the broken/mismatched automation state.
Likely failure conditions
The issue may happen when one or more of these are true:
automation.tomlis invalid TOML.automation.tomlcontains a UTF-8 BOM.- The app-side automation registry is out of sync with the TOML file.
- An active automation has a stale/past
next_run_at. - A local automation folder exists but the app registry row is missing or mismatched.
Expected behavior
- Invalid TOML should be shown as a configuration error, not as a silently missing automation.
- Registry/TOML mismatch should be detected and surfaced.
- Active recurring automations should not disappear from the Current list without an explanation.
- Daily schedules should be displayed as daily schedules, or weekly-all-days representation should be clearly explained.
- The app should provide a resync/repair diagnostic or warning.
Suggested checks
Codex App could validate:
- TOML parse status
- UTF-8 BOM presence
- automation id vs folder name
- registry row existence
- TOML/registry mismatch for status, RRULE, cwd, model, and prompt hash
- stale
next_run_atfor active recurring automations
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗