Environment
- ChatGPT Plus, Windows PC; tested during a session using the web interface and ChatGPT desktop app.
- Features: MCP Events in Work/Cloud and an ordinary one-time scheduled text task.
- Date: October 6, 2026, Europe/Brussels (UTC+2).
Bug
A task runs successfully and its answer is available in the task execution and email notification, but the answer is missing from the original conversation. The email’s “View message” link opens the original conversation, where the corresponding answer is not visible.
The task setting explicitly says “Dezelfde chat bij elke uitvoering” (same chat for every execution). Asking explicitly in the task prompt to continue the original conversation and post a new assistant response there did not change the outcome.
Reproduction
- Create a one-time scheduled task from an existing conversation.
- Select the same chat for every execution.
- Ask for a distinctive text marker and an answer in the original conversation.
- After execution, check the task run, email notification, and original conversation.
In our dry text test, the requested marker was “DROGE TEST D”. It appeared in the email answer, but no corresponding assistant message appeared in the original chat. No external tools or jobs were required for that test.
We also observed the same symptom with a custom MCP event subscription: the gateway reported delivery, ChatGPT recorded a task execution, and the automatic answer confirmed that the job-status and job-result tools worked. The result appeared at the task execution rather than visibly in the originating chat. A browser extension used in an earlier proof of concept was disabled for that test.
Expected behavior
With “same chat for every execution” selected, the completed answer should be visible in the original conversation. The notification link should lead to the actual answer.
The MCP Events guide says ChatGPT receives the event in the subscribed chat, and the scheduled-task guide describes returning to an existing chat with its context:
Diagnostics
- MCP event test: recorded execution at approximately 19:45:48 Brussels time.
- Dry scheduled text test: recorded execution at approximately 19:58:19 Brussels time.
- Both tasks have the same stored conversation_id (private identifier omitted).
- No visible error was reported in these executions.
- These observations establish successful execution, but do not establish whether the missing message is a routing or rendering problem.
Could you clarify whether “same chat” guarantees an answer in the original chat timeline, or only reuse of its context? If the answer should be displayed there, please investigate the missing result and notification-link behavior.
Related reports:
The second report concerns a different environment but describes a similar symptom.