Skip to content
Independent guide · Dots Bot

Troubleshooting

Diagnose access, connections, stalled work, and limits in a useful order.

Updated 4 October 2026 · Independent of OpenAI

Troubleshooting — Find the next useful check
Visual guide to Troubleshooting

Start with what the interface actually says. Account eligibility, an app permission, a waiting approval, and a usage allowance are different failure modes.

Diagnose access, connections, stalled work, and limits in a useful order. State the question tightly enough that an answer can be checked against a known file, page, account, or date.

Editorial route

Find the failed boundary first

There is little value in reconnecting an app when the real problem is rollout, or upgrading a plan when the task is waiting for approval. Begin with the exact interface message and the task’s Activity record. Then inspect the relevant connection or account. Before any retry, check the target service for a completed action. The guides below follow each failure mode to a safer next check.

Choose a route

Guides in this section

Pick the specific page that matches the work in front of you. Each guide has a flat URL, a concrete review point, and links back to this overview. If the request spans several guides, finish one bounded piece before adding the next.

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

How to use this section

Use exact error, plan, device, task and time as the starting point. Include enough context to interpret them, but avoid passing unrelated personal or workspace material.

A useful deliverable

A narrowed cause and safe next check. Keep the date and source close to any claim that may change before you act.

Worked situation

How this plays out in practice

"Dots is broken" could mean no access, a disconnected app, a waiting approval, or an exhausted Work task allowance. Each has a different remedy. This case tests whether a draft notices the important constraint rather than flattening everything into a summary. Gather the known facts first, then decide what else to verify.

Record the exact message and time, then inspect account eligibility, Activity, Scheduled, connections, and the target service in that order. Retain the key reference and the date so a future revision does not have to reconstruct the whole task.

A practical sequence

Run a bounded first pass

1. Establish the starting point

Specify exact error, plan, device, task and time; add the relevant location or workspace only where it changes the interpretation.

2. Request a reviewable draft

Check plan and rollout, then the dot’s Activity and Scheduled views, then the relevant connection and account. Record the exact message and time before retrying. Ask for a smaller, verifiable result if the source set is too large for one pass.

3. Decide the next action

Pause where the consequence begins: do not duplicate a purchase, send, or edit. A proposal is useful even when the action is postponed.

Editorial judgment

Where a plausible answer can fail

Blind retries can duplicate an external action. First confirm whether the previous attempt wrote a file or sent a message. If the supporting material is incomplete, a qualified answer is stronger than a confident invention.

Avoid repeating an external action if the previous attempt may have succeeded. Check the target app for completed changes first. When a check fails, keep the original observation and the exact condition under which it failed.

Where to go next

Connect this result to the right follow-up

If you are new to the product, Get Started & Trust helps establish the account and permission basics before you use this section as a working plan. Once this page has answered its narrow question, a nearby guide can carry the work forward without changing the original brief.

For a closely related outcome, open Dots Not Showing in Your Account. That guide focuses on check rollout and account eligibility when Dots is absent. 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 App or Plugin Connection Not Working is a better fit: find out whether the problem is sign-in, permission, app capability, or account mismatch. A new deliverable should have its own date, owner, and acceptance check.

Before you reuse this result elsewhere, look at Get Started & Trust 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

Which guide should I open first?

Open the child guide closest to the result you need: a narrowed cause and safe next check. Start with its inputs and review gate, then come back to this overview for adjacent tasks.

What information matters most for troubleshooting?

Start with exact error, plan, device, task and time. Start with what the interface actually says. Account eligibility, an app permission, a waiting approval, and a usage allowance are different failure modes. Give the exact source or account where a decision depends on it.

How do I combine two related workflows?

Define separate results and approval points. Avoid repeating an external action if the previous attempt may have succeeded. Check the target app for completed changes first.

What would a useful result look like here?

A narrowed cause and safe next check. 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?

Blind retries can duplicate an external action. First confirm whether the previous attempt wrote a file or sent a message. 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.