A dot may wait for approval, sign-in, a connected app, a decision, or a local computer to come online. The Activity view identifies the task and progress.
Inspect the waiting state before restarting a task. Think of this as a small research or drafting assignment. Source, date, uncertainty, and a review point make the outcome usable.
First checks
Identify the state before changing anything
What the interface says
Copy the exact error or waiting message, task name, account, and time. An access problem, an approval request, and a usage limit require different follow-ups.
What already happened
Look in Activity and the connected service for partial results. This matters before a retry that could duplicate a message or an edit.
Define the task
What to prepare before you begin
Before you open another connection, assemble task, last update, pending request. Check whether those materials already answer the question you intend to ask.
A useful deliverable
Safe continuation or cancellation path. Add a short list of unresolved questions so the reviewer can decide what needs a fresh source.
Worked situation
How this plays out in practice
A task that appears idle may have paused for a site sign-in or a request to approve a particular action. The small complication in this example changes the right next step. Ask for alternatives and for the assumption that would reverse the recommendation.
Open the specific Activity item, read its pending request, and verify any target URL, account, recipient, or document before responding. The result should remain useful when someone checks it with the original document or account open.
A practical sequence
Run a bounded first pass
Define the scope around task, last update, pending request. Tell the assistant when to stop searching and which missing fact should come back as a question.
Open Activity and the exact task. Read the pending request, verify the target account, and respond or redirect it. For local work, check the computer and app state. Ask for a smaller, verifiable result if the source set is too large for one pass.
Confirm the planned effect against avoid duplicate external actions. Ask for a change list if the next step would modify an external system.
Editorial judgment
Where a plausible answer can fail
Restarting an uncertain write task may repeat the action. Check the connected service for partial completion first. Check the claim with the largest downside first. A missing qualification can matter more than a rough paragraph.
A restart could repeat an external action. Check the target service for partial completion first. When evidence falls short, narrow the claim and name the missing document or decision.
Where to go next
Connect this result to the right follow-up
The Troubleshooting hub gives you the broader route and neighboring tasks. Return there when the present job has produced a result, rather than adding an unrelated responsibility to the same brief. The next useful question is often adjacent to this one, but it deserves its own source set and review.
For a closely related outcome, open Dots Usage Limit Reached. That guide focuses on distinguish conversation access from deeper work allowances. It may use some of the same context, but you should confirm the source and the decision point again. If your next question is about a different angle, Dots Not Showing in Your Account is a better fit: check rollout and account eligibility when Dots is absent. A new deliverable should have its own date, owner, and acceptance check.
Before you reuse this result elsewhere, look at Track Activity and Review Results for the wider product or review boundary. Take forward the verified facts and leave behind any assumption that was specific to this example. If the source has changed since the draft was made, update the relevant claim first. The purpose of the link is to make the next step more precise, not to imply that every connected guide is needed for every reader.
Adapt this
Build your own task brief
Edit the bracketed information and any sentence that does not fit your account. This is a suggested workflow, not a promise that your dot has access to a particular app or feature.
Your review
Check before moving on
Tick what you have actually checked. Your progress stays on this device for this page and can be cleared at any time.
0 of 4 checked
Questions
Frequently asked questions
What should I check before trying again?
Use the scenario on this page as a small test. Open the specific Activity item, read its pending request, and verify any target URL, account, recipient, or document before responding. Keep a source and a date beside any detail that can change.
What information matters most for dots task stuck or waiting for approval?
Start with task, last update, pending request. A dot may wait for approval, sign-in, a connected app, a decision, or a local computer to come online. The Activity view identifies the task and progress. Give the exact source or account where a decision depends on it.
How do I preserve the error for support?
A restart could repeat an external action. Check the target service for partial completion first. The relevant access, audience, and consequences determine what you should approve.
What would a useful result look like here?
Safe continuation or cancellation path. It should make assumptions visible and leave a trail to the source, especially for dates, prices, permissions, or changing product details.
What is the common failure in this situation?
Restarting an uncertain write task may repeat the action. Check the connected service for partial completion first. Review that issue in the actual output instead of treating a polished presentation as proof.
Where can I check the current details?
Follow the official source linked below and inspect your account where access matters. This page was revised in October 2026; availability, terms, and product behavior can change.
Source for current product details: official OpenAI documentation or announcement ↗. The worked situations and briefs on this independent site are editorial examples. Confirm current access and details in your account. Editorial policy.