Troubleshooting

The failures we have actually seen, and what each one means.

“Authorization failed” when connecting

The approval went through but the assistant could not read anything afterwards. Almost always this means the account that approved it is not a member of the organization it was approved for — support access to a floor is not the same as membership of it.

Check under People Access that you are listed as an owner or admin of that organization, then connect again. If the approval screen offers you a company you do not administer, tell us: the screen and the data are meant to read the same list.

ChatGPT has no option to add a connector

Developer mode is off. Turn it on under Settings → Connectors → Advanced settings, then the option appears under Connectors. If Advanced settings is not there at all, your plan does not include it yet — it is a beta feature and OpenAI has been rolling it out by plan.

It says it has no data, but the dashboard shows some

Usually a stale tool list. An assistant caches what it can do when it connects, and it will not notice new capabilities on its own.

Remove the connector and add it again. That forces a fresh list. If it still claims data is missing that you can see on screen, that is a bug worth reporting — an assistant denying something the dashboard displays is the failure we care most about.

It asks which organization every time

Expected, if your connection covers more than one. A question that does not name a company is refused rather than guessed, because a default would mean one client's figures answered under another client's name.

Name the floor in the question — “how did Blueprint do yesterday?” — and it will not ask again for that one. If you only ever want one organization, reconnect and tick only that one.

A figure disagrees with your own records

Ask the assistant to break it down rather than asking whether it is right. “Why is cash collected today $7,000? List the payments.” The answer names each payment, its source, and the deal behind it, and the gap is usually obvious once it is itemised.

The three most common causes:

• Collected is coming from the CRM rather than a processor, so it reflects what was sold. See when collected is not cash.
• A deal is dated in the future and counts from the moment it was marked won.
• A CRM status counts as won when you do not think of it that way — a “balance owed” stage, for instance.

An answer was confidently wrong

Assistants explain figures they do not fully understand, and ours is no exception. Two habits help: ask it to show the rows behind any figure it quotes, and ask it what “collected” means for your organization before trusting a revenue number.

If it quotes an amount that is a hundred times too large or small, that is a real bug — report it rather than working around it.

A connection stopped working

Access is re-checked on every request, so it stops the moment any of these change:

• The person who connected it was removed from the organization.
• Somebody pressed Disconnect under People Access.
• The credential was used in a way that suggests it was copied — a sign-in token presented twice, for instance. The connection is revoked outright rather than the one request being refused, on the basis that two parties holding one credential means one of them should not.

Reconnecting takes a few seconds and is the fix for all three.

Something here wrong or missing? Tell us — these pages are part of the product.