Run Now for cron automation opens a blank thread

Open 💬 3 comments Opened Jun 8, 2026 by chaox2605-art
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

26.602.40724

What subscription do you have?

Plus

What platform is your computer?

OS: Windows

What issue are you seeing?

Run Now for cron automation opens a blank thread with title only.

What steps can reproduce the bug?

  1. Open an existing cron automation.
  2. Click "Run Now".
  3. A new thread opens.

What is the expected behavior?

The automation prompt should be submitted as a user_message and the run should start.

Additional information

Actual:
A blank thread opens with the automation title only. The session contains only session_meta:

  • no user_message
  • no automation prompt
  • tokens_used=0
  • no assistant response
  • no inbox result
  • no automation memory.md

This makes Run Now unusable for cron automations.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 2 months ago

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

  • #25751

Powered by Codex Action

chaox2605-art · 2 months ago

blank thread
title only
session_meta only
no user_message
tokens_used=0

chaox2605-art · 2 months ago

I found that cron automation fails when the cwd points to a Codex project/workspace folder. It creates a blank thread with title/session_meta only and never submits the prompt. Running outside a project folder appears to avoid the issue.