> For the complete documentation index, see [llms.txt](https://developers.spiffy.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.spiffy.co/connectors/spiffy/troubleshooting.md).

# Troubleshooting

## "Unauthorized" or it keeps asking you to sign in

The server returned a `401`. Usual causes:

* The authorization expired or was revoked. Remove and re-add the connector in your client to run the OAuth flow again.
* The Spiffy account or app was disabled. If your login or the connector app was turned off, reconnecting won't help. Reach out to Spiffy support.
* No account access. The grant has to include at least one account. If every account grant was removed, reconnect and approve one.

## "Account is required" on a write

When your connection spans several accounts, write tools won't guess which one to use. Name it in your prompt:

> *In the Acme Co account, refund order 1234.*

Reads default to one of your accounts on their own; only writes need an explicit account when more than one is in reach. See [Accounts and scopes](https://developers.spiffy.co/connectors/spiffy/setup.md#accounts-and-scopes).

## A tool you expected is missing

* Scope not granted. Each tool needs its scope. If you didn't grant the `promos` scope, the promotion tools won't be callable. Reconnect and approve what you need.
* Read vs. write. A tool that changes data needs write access to its scope. Granting read only exposes the `list_*` and `get_*` tools, not `create_*` / `update_*` / `delete_*`.

## Date filters look off by a few hours

Spiffy stores timestamps in UTC and ignores time-zone offsets in date strings. If a filter seems shifted:

* Ask for UTC explicitly, or
* Give a clear local time so the assistant converts it (for example, *"orders created after 9am Pacific on May 1"*).

The assistant has `get_utc_time` and `convert_to_utc` for this. If results still look wrong, ask it to recompute the range in UTC.

## "Rate limit" or "monthly quota" errors

Connector calls count against your account's monthly Spiffy API quota, shared with your HTTP v2 API usage. A burst can hit the per-minute limit, and heavy use can exhaust the monthly quota. Wait and retry for rate limits. For quota, check your plan's limits or contact support.

## A write didn't take

* Make sure you approved the confirmation. The assistant won't run a write until you do.
* Check the tool's response for a validation error. The v2 API returns specific messages (a required field, a value out of range), and the assistant passes them back so you can fix the request.
* If you have multiple accounts, confirm you were working on the right one.

## Still stuck?

Reach out to Spiffy support with what you asked, which tool failed, and the error message. Every call is in your Spiffy audit log, which helps support trace it.
