Business workflow guide
ChatGPT dots task stuck? Check what it is waiting for
AI-assisted guidance prepared for Blue Canvas from the official sources linked below. The examples are proposed workflows, not reports of firsthand product testing.
A task that appears stuck may be waiting for a decision or access it does not have. Before repeating the request, inspect the original task and identify the last confirmed state. Repeated instructions can add ambiguity without resolving the reason work stopped.
Open the task, not just the main conversation
OpenAI directs desktop users to the dot's profile and Activity to inspect a task's progress, files, results and requests. A pending request may concern a decision, app connection, sign-in or approval. Read that request before deciding whether to continue.
Match the task by its purpose and input, not only a similar title. Write down the last output you can actually inspect and the question still unanswered. If no request or useful status is visible, record that uncertainty; do not diagnose an outage from silence alone.
This guide concerns an existing task you can identify. If dots is absent from your account altogether, use the separate access guide rather than treating it as a stalled task. It does not promise a repair for every error or an account-specific service status.
Product source: OpenAI's official documentation, checked 31 October 2026.
Classify the blocker before doing anything
A request for a missing source and a request to send a message require different responses. Do not grant a broad permission simply to clear a waiting state. First ask whether the requested action is part of the task you intended to authorise.
Use the following as a diagnosis record, not a list of fixes to perform automatically. Leave the task waiting if the account, source or consequence is unclear. A blocked result can be the correct outcome for a boundary you deliberately set.
| Observed request | Question to resolve | Bounded response |
|---|---|---|
| Missing detail | Which decision is needed to continue? | Answer that question for the named task |
| Source unavailable | Is the intended source accessible and authorised? | Ask for the exact missing source; do not substitute unrelated data |
| Approval needed | Does the action match the agreed scope? | Review it or leave it blocked; do not bypass the check |
| No clear request | What is the last verifiable state? | Request a status and limitation report before retrying |
Check the relevant connection, not every connection
OpenAI says local work needs the connected computer online with the ChatGPT app open. Its cloud browser has separate sessions from your personal browser, and plugin access depends on the connected account and permissions. Check the dependency named by this task.
If the task needs a local sample file, confirming that you can chat on your phone does not check that file's availability. If it names a connected service, verify the intended account before proceeding. Do not disconnect unrelated services or repeatedly reconnect everything as an experiment.
Never paste passwords, session cookies, API keys or one-time codes into a task conversation to get around a blocker. Do not follow a request to disable safeguards. Use only the product's legitimate account controls after checking the request and destination; otherwise leave the task blocked and seek the appropriate support.
Product source: OpenAI's official documentation, checked 31 October 2026.
Request a diagnosis without authorising a retry
A good status response should distinguish what was attempted from what was completed. If the original task involved an external action, inspect its authorised destination before any repeat attempt. An uncertain result is not evidence that nothing happened.
For a document-only test, ask where the output can be opened and which source revision it used. For a blocked read, ask what input is missing. Keep the next decision narrow enough that the reviewer can understand its effect.
Adapt this example to your approved task
For [existing task reference], report the last confirmed state, any pending request, the exact missing input or connection, and outputs already created. Separate confirmed facts from unknowns. Do not retry external actions, send messages, change permissions, reconnect accounts, edit files or alter schedules. If the next step needs a decision, explain that specific step and wait. Do not request secrets in the conversation.
Continue the intended task and inspect the result
OpenAI explains that delegated tasks have their own conversations and do not automatically receive every exchange with the dot. Make sure a clarification reaches the identified task instead of assuming the main conversation updated it.
Once the blocker is understood, decide separately whether to continue. Do not start a replacement merely because it has a cleaner title. Compare the next output with the original acceptance criteria and open the file or result it names. If the source is still unavailable, retain the limitation rather than accepting an invented substitute.
For a persistent unexplained problem, prepare a sanitised support record: task reference, approximate time and time zone, visible error wording, what was expected and checks already performed. Exclude source contents, credentials and private records. This record describes the problem; it does not establish its technical cause or justify changing unrelated automations.
Product source: OpenAI's official documentation, checked 31 October 2026.