# Possible bug: Codex Automations (Beta) test runs stay IN\_PROGRESS with no output

**URL:** <https://community.openai.com/t/possible-bug-codex-automations-beta-test-runs-stay-in-progress-with-no-output/1375778>\
**Category:** Codex\
**Tags:** windows-app\
**Created:** [March 5, 2026, 12:13pm UTC](https://community.openai.com/t/possible-bug-codex-automations-beta-test-runs-stay-in-progress-with-no-output/1375778 "2026-03-05T12:13:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joao\_Martins](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/joao_martins/32/675116_2.png) [@Joao\_Martins](https://community.openai.com/u/Joao_Martins)\
**Post date:** [March 5, 2026, 12:13pm UTC](https://community.openai.com/t/possible-bug-codex-automations-beta-test-runs-stay-in-progress-with-no-output/1375778/1 "2026-03-05T12:13:44Z")

</div>

Hi everyone, sharing a reproducible issue I hit while testing Codex Automations (Beta).

Environment:

- Windows + WSL workflow
- Codex Desktop, codex-cli 0.108.0-alpha.8
- Automation status: ACTIVE
- CWD points to a WSL repo path (UNC style)

Repro:

1. Create/update an automation (also tested with a minimal one-line prompt).
2. Click Test (and also waited for scheduled trigger).
3. Check Automations/Inbox for output.

Expected:

- Run completes and produces an inbox/thread result.

Actual:

- Test appears briefly then disappears.
- No inbox output is created.
- Local automation DB shows:
  - `automations.last_run_at` updates (trigger seems to fire),
  - `automation_runs` row is created,
  - status remains `IN_PROGRESS` indefinitely,
  - `inbox_items` stays empty.

Troubleshooting tried:

- Restarted app (normal + admin).
- Retried with different WSL UNC path variants.
- Simplified prompt to minimal output.

Looks like trigger bookkeeping works, but execution/result materialization stalls. Happy to provide additional redacted diagnostics if useful.

---

<div class="post-metadata">

**Author:** ![EricGT](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/ericgt/32/20571_2.png) [@EricGT](https://community.openai.com/u/EricGT)\
**Post date:** [March 5, 2026, 12:44pm UTC](https://community.openai.com/t/possible-bug-codex-automations-beta-test-runs-stay-in-progress-with-no-output/1375778/2 "2026-03-05T12:44:03Z")

</div>

It appears you are using the new Codex Windows app and reporting a problem.

If so then see this [reply](https://community.openai.com/t/the-codex-app-is-now-on-windows/1375704/6)

---

<div class="post-metadata">

**Author:** ![Joao\_Martins](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/joao_martins/32/675116_2.png) [@Joao\_Martins](https://community.openai.com/u/Joao_Martins)\
**Post date:** [March 5, 2026, 1:26pm UTC](https://community.openai.com/t/possible-bug-codex-automations-beta-test-runs-stay-in-progress-with-no-output/1375778/3 "2026-03-05T13:26:04Z")

</div>

Hi @EricGT , you mean i should add possible bugs on the form, under “Please share detailed feedback to explain your decision above.” ?

---

<div class="post-metadata">

**Author:** ![EricGT](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/ericgt/32/20571_2.png) [@EricGT](https://community.openai.com/u/EricGT)\
**Post date:** [March 5, 2026, 1:42pm UTC](https://community.openai.com/t/possible-bug-codex-automations-beta-test-runs-stay-in-progress-with-no-output/1375778/4 "2026-03-05T13:42:54Z")

</div>

> [@Joao\_Martins](#):
>
> i should add possible bugs on the form

Yes.

* * *

The other official way is to use the [GitHub OpenAI Codex issues](https://github.com/openai/codex/issues) by first searching to see if this has not been reported. If it has just add a thumbs up to the current issue. If not create a new issue.