Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[ChatGPT iOS][Scheduled Tasks] Push opens correct conversation, but notified result is missing from history

Open
  • Is something wrong?
#52,357 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
8/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust, swift
Domain
backend, mobile

Research direction

The report is a user-facing symptom with no code location: a scheduled task's push notification opens the right conversation, but the notified assistant message is absent from history. Nothing in the payload names a file, test or entry point, so the first step is to find where scheduled-task results are persisted and rendered, which the issue does not identify. Done would mean the notified output stays visible in the linked conversation after the push is opened; this is a cross-surface investigation rather than a newcomer task.

Written by the indexing model from the issue text.

Description

automations bug iOS session

Summary

On 8 October 2026, a normal ChatGPT Scheduled Task delivered a push notification containing its result/summary to my iPhone. Tapping that notification opened the correct ChatGPT conversation at the current/bottom position, but there was no corresponding assistant message for that run in the visible conversation history.

The exact notified output could not be recovered from the visible chat. I had to ask ChatGPT to rerun the task and print the result into the conversation; the manual rerun then produced a visible result.

I originally added this reproduction under a local desktop heartbeat report. This standalone issue identifies the affected surface as ChatGPT Scheduled Tasks on iOS, rather than only Codex Desktop heartbeats.

Original report: https://github.com/openai/codex/issues/41995#issuecomment-6059594410

Environment

  • Subscription: ChatGPT Pro.
  • Client: ChatGPT iOS app 1.2026.267.
  • OS: iOS 26.5.2.
  • Timezone: Europe/Amsterdam, CEST (UTC+02:00).
  • Observation date: 8 October 2026.

Observed sequence

  1. The scheduled task ran at approximately 07:57:56 Europe/Amsterdam.
  2. Its task record was updated at approximately 07:58:19.
  3. A ChatGPT push containing the scheduled result/summary appeared on the iPhone.
  4. I opened the push shortly afterward.
  5. It deep-linked to the intended ChatGPT conversation.
  6. The conversation was already at its current/bottom position, rather than an old scroll location.
  7. No new assistant message for that scheduled run was present in the visible history.
  8. The original notification result could not be recovered from that history.
  9. I manually requested a rerun and direct output in the conversation. The manual rerun produced a visible result.

A separate scheduled task was checked and was not responsible for this notification.

Expected behavior

When a scheduled task notifies the user, the exact notified assistant output should remain visible in the linked conversation after the notification is opened, the app is resumed, or the conversation is reopened.

The push should provide a reliable path to the original result, rather than being the only transient place where the user can see it.

Impact

A notification can contain actionable information, yet opening it leaves the user with no matching result. A manual rerun is additional work and cannot be assumed to reproduce the exact original output.

Notification delivery worked in this occurrence. The failure was the absence of the corresponding result in the conversation.

Related reports

  • #41995 and my original comment linked above describe similar missing scheduled-result visibility on other surfaces.
  • My separate Windows ChatGPT desktop completed-history/mode failure: #52355.
  • My separate acknowledgement-only execution failure: #52356.
  • #52086 tracks a different iOS issue involving missing activity indicators.

I cannot establish whether this is history rendering, persistence, or another result-delivery problem, or whether the local heartbeat report shares the same cause. Please investigate the scheduled run → push → durable conversation-result path and provide any supported recovery route, fix, or ETA.

No private task IDs, conversation links, notification contents, files, or project materials are included.

Dominant language
Rust
Stars
129k
Forks
20.3k
Avg merge
1m
Merged PRs (30d)
998

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.