# Scheduled task finishes but the reply vanishes from the original chat > Source: > Published: 2026-10-06 19:38:18+00:00 # Scheduled task finishes but the reply vanishes from the original chat The “same chat” setting in [ChatGPT](https://promptcube3.com/en/tags/chatgpt/) isn’t doing what it says on the tin. When you schedule a task to run inside an existing conversation, the work gets done, but the final answer often stays hidden in the task execution log instead of appearing in the message timeline you’re actually looking at. It’s a subtle routing glitch that breaks the illusion of continuity. If you rely on scheduled tasks or [MCP](https://promptcube3.com/en/tags/mcp/) events to keep a context alive, you need to verify where the output lands before building dependent workflows on top of it. ## How the bug manifests The issue shows up in both the web interface and the ChatGPT desktop app on Windows. You create a one-time scheduled task from an active conversation and explicitly select the option to keep the task within the same chat for every execution. Here is what happens: 1. The task runs successfully at the scheduled time. 2. You get an email notification with a “View message” link. 3. Clicking that link takes you back to the original conversation. 4. The answer is not there. The result sits in the task execution record and the email, but the chat timeline remains empty. This happened even when asking the model to explicitly post a new assistant response in the original thread. ## Two ways to reproduce it You can trigger this with simple text or via MCP event subscriptions.**Dry text test** Ask the scheduler to output a specific marker, like `DROGE TEST D`. When the task finishes, that marker appears in the email notification. However, scrolling through the original chat history yields nothing. No tools or external jobs are involved here, just a basic text generation task.**MCP Event subscription test** Set up a custom MCP event subscription. The gateway reports successful delivery, and ChatGPT records the task execution. The automatic answer confirms that the `job-status` and `job-result` tools functioned correctly. Yet again, the final result shows up in the isolated task execution view rather than visually in the originating chat stream. Note that browser extensions were disabled during this check to rule out local rendering interference. ## What’s happening under the hood Both tests share the same `conversation_id`. In the observed cases, the scheduled text task executed at roughly **19:58:19** Brussels time, while the MCP event test logged at **19:45:48**. Since the ID matches, the backend knows which chat belongs to which context. The failure isn’t a context loss; it’s a display or injection error. This matters because previous behavior allowed a task to read the output of a prior task within the same window. Now that outputs land in separate silos, chained tasks can no longer directly influence each other within a single flow unless you manually stitch the context back together. ## What to do next Until OpenAI fixes the injection pipeline, treat “same chat” as a context hint, not a guarantee of visibility. - **Check the task log first.** Always verify the execution record for the actual output before assuming the chat thread updated. - **Use explicit markers.** Having a unique string helps you quickly grep or search for the result if you pull the chat history into another tool. - **Don’t chain blindly.** If your next step depends on the previous task’s output being visually present in the chat for a subsequent model read, add a manual confirmation step or use a script to fetch the task result directly via API if available. The feature works technically, but the UI feedback loop is broken. [Next Gemini 3 Pro's Disappearance from Google AI Studio →](https://promptcube3.com/en/threads/9811/) ## All Replies （1） Want a live back-and-forth? [Join the global AI chat room](https://promptcube3.com/en/chat/) — login to talk. I got burned by this too. My scheduled task finished, but the reply was buried in the execution log.