> ## Documentation Index
> Fetch the complete documentation index at: https://docs.goosybear.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> The things that actually go wrong in Goosy Bear, and the one check that settles each of them.

Each entry below is a symptom, the **one check** that tells you which problem
you have, and what to do about it. Work down the list rather than across — the
check is usually faster than the guess.

If none of these is your problem, ask. [Support](/help/getting-help) is in your
own menu, top-right.

## You cannot sign in

**Check:** are you sure you have an account? Accounts in Goosy Bear are created
by invitation — **there is no sign-up form**.

If you were invited and the password is not working, use **Email me a sign-in
link** on the sign-in page and click the link that arrives; it signs you in
without a password. **Continue with Google** works if that is how your email is
set up. If none of the three work, ask an owner or admin on your account to
check the invitation reached the right address.

## Something you asked for has not happened

**Check: open [Review](/work/reviews).** It is almost always there.

Goosy prepares work; he does not publish it, spend on it, delete anything or
change anyone's access on his own. All four stop at an approval gate, and
everything waiting on a decision collects in that one queue.
[How approvals work](/how-approvals-work) is the whole picture.

## A post did not go out

**Check: the band above the grid in [Schedule](/work/schedule).** When a publish
fails, a band appears there naming the platform, the time it was due, and what
happened. The same failure shows on your dashboard as a **Publish check**
waiting on you.

The usual cause is a connection that dropped — see the next entry. Note that
**retrying from that band is not available yet**: the only action there today is
**Cancel**. Cancel it, fix the connection, and re-create the piece.

## A connection stopped working

**Check: [Settings → Integrations](/setup/integrations), then the Attention
filter.** It narrows the
page to exactly the connections that need you. A card in that state says the
latest health check failed and when it last succeeded; a banner at the top of
the page names the provider too.

Press **Reconnect** and approve the access again at the provider. Access
expires, passwords change, and people remove apps at the provider's end — this
is normal maintenance rather than a fault.
[Connect your channels](/start/connect-your-channels) has the full state table.

## Goosy keeps asking about small amounts — or spent without asking

**Check: Settings → Account → Spending & approvals**, and read which of the
three choices is selected.

* **Ask me every time** — everything that costs money stops for you. If Goosy
  is asking about small things, this is why.
* **Work within a monthly budget** — work that fits inside the budget **runs
  without asking you first**. That is the point of setting one, and it is the
  setting people are most often surprised by.
* **Describe it in your own words** — your sentences, read into a budget you can
  check before saving.

Two independent switches sit under the same section — *require my approval
before money is spent* and *require a client sign-off too*. Either one turned on
sends the request to **Review**.

## The numbers on Analytics look wrong or empty

**Check: the line at the top of [Analytics](/work/analytics)** — *2 of 6 sources
connected · last 4 weeks*. It tells you how much of the picture the page has
before it shows you anything.

Nothing on that page is estimated. A card whose source is not connected says
**not connected** and offers the connection rather than drawing an empty chart,
and a missing day in a chart is a day your platform did not report — not a zero.
If a number looks wrong, first confirm the source behind it is connected and the
period is the one you meant.

## You cannot find something you know you made

**Check: the workspace button in the top bar** — you may be looking at a
different workspace.

A workspace is a closed box: its content, settings, connected channels and
knowledge are its own, and nothing crosses between them. Most people have one
workspace and never think about it; if you run several, this is the first thing
to check. See [Your data and privacy](/your-data-and-privacy).

## You are not getting the emails you expected

**Check: Settings → Notifications.** It is a grid — one row per kind of thing
that happens, one column per way of reaching you — so the answer is at the
crossing point.

Two things catch people out:

* **The summary is a separate switch.** Choosing *email as one summary instead*
  does not turn the **Email** column off; rows with Email still on keep emailing
  as things happen.
* **Turning off *In the app* stops the bell too**, not just the email.

Whatever you switch off, work waiting on your decision stays in
[Review](/work/reviews) until you decide it.

## Texts are not arriving

**Check: the same grid — texts exist for two rows only.** *Waiting on your yes*
and *publishing went wrong* are the only kinds that send a text; every other row
shows a dash instead of a switch, because it does not send texts at all.

Texts also start only once your phone is verified.

## A support reply never showed up in the conversation

**Check: the bell in the top bar.** The reply arrives as a notification carrying
the person's full message.

Re-opening the Support conversation does not show you the reply — the
conversation does not redisplay what was said before. There is no ticket portal
to check and no reference number to keep. See
[Getting help](/help/getting-help).

## An API call is being refused

**Check: the status code first, then `ok`.** A `4xx` means the request never
reached the action; a `200` means it did, and `"ok": false` in the body is the
action itself declining with a reason.

**Branch on `ok`, never on the status code.**
[Errors and refusals](/api/errors-and-refusals) names every refusal, what it
means, and who can clear it — including the four that are about the platform
rather than about you, where minting another key is the most common wasted step.

## You cannot create an API key

**Check: whether you hold *Use the API and MCP*.** It is a permission like any
other on your account, and an owner or admin grants it under **Settings →
Members & invites**.

[Who can use the API](/permissions) covers who has it by default and how it is
granted.

## Still stuck

Open **Support** from your own menu and describe what happened, what you
expected, and where you were. Goosy answers what he can and raises a ticket for
the rest — [Getting help](/help/getting-help) explains what happens next.