Existing-chat heartbeat run completes but Scheduled inbox remains on the previous run

Summary

A recurring Codex Desktop automation attached to an existing chat completes successfully and appends its result to the target chat, but the Scheduled inbox does not surface the latest run. It remains on the previous accepted/read run.

Environment

• Codex Desktop on Windows 11
• Automation kind: heartbeat
• Target: existing chat
• Weekly recurrence

Steps to reproduce

1. Create a recurring Scheduled task inside an existing chat.
2. Allow the first run to complete and open/read its Scheduled result.
3. Allow the next scheduled occurrence to complete.
4. Confirm that the result appears in the existing chat.
5. Open Scheduled.

Actual behavior

• The second run completes and updates the automation's last-run timestamp.
• Its assistant output is appended to the target chat.
• The Scheduled inbox still displays the previous run title and read state.
• No new inbox item or refreshed unread indicator appears.

Expected behavior

The existing chat should continue to be reused, but each completed run with findings should refresh the Scheduled entry and unread indicator, consistent with the Automations documentation.

Sanitized local evidence

• The automation-run record is keyed by the target thread ID.
• The heartbeat reuses the same target thread ID.
• The existing row remains accepted/read with the previous inbox title.
• No inbox row is created for the later successful run.
• The automation's last-run timestamp and the chat rollout both prove that the later run completed.

Notes

This is not the same as heartbeat automations failing to execute. Execution and delivery to the existing chat succeed; only Scheduled inbox visibility fails.

Start by reproducing the heartbeat automation with an existing chat, then trace the completion path and the Scheduled inbox update path. Compare the later successful run with the previous accepted/read row and verify that each completed run with findings refreshes the entry and unread indicator without creating a separate target chat.