Skip to main content
Here are answers to typical issues you might encounter when using the Abundly platform. If your issue isn’t covered here, and you can’t an answer by searching this site, then please contact support@abundly.ai. We are happy to help!
Open Help & support in the sidebar (above your profile), then choose Contact support. That opens a structured message to our support team with your verified email as the reply-to address, and it can include useful context from your session.For general questions, use Documentation or Getting started from the same menu, or email support@abundly.ai.
The “Overloaded” error occurs when the LLM (such as Anthropic/Claude’s server) is experiencing high traffic.How to resolve:
  1. Wait 5-10 minutes and try again
  2. This is a temporary issue that usually resolves on its own
  3. If it persists after 15+ minutes, contact support@abundly.ai
You can also try switching to a different LLM temporarily. See Model Selection for details.
Model providers enforce daily and monthly token quotas at the account level. When a run hits one of these long-term limits, Abundly ends the run immediately and shows a Provider capacity limit reached message — rather than retrying for ~30 minutes to no benefit.This applies to every model provider, including Anthropic, OpenAI, Google and xAI.This is different from:
  • Short-term rate limits (TPM/RPM) — these are still auto-retried transparently and usually resolve within seconds.
  • “Overloaded” errors — caused by provider-wide traffic spikes and also auto-retried. See the entry above.
How to resolve:
  1. Wait for your quota window to reset. Exact timing depends on the provider — daily quotas typically reset at midnight UTC, and monthly quotas at the start of your billing period.
  2. Temporarily switch to a different model or provider while you wait. See Model Selection for details.
Every message you send includes the whole conversation so far, and there are two limits it can run into. The model’s context window is the total amount of text, files and history it can hold at once — when the conversation grows past it, Abundly shows Model context limit reached. Separately, providers cap the raw size of a single request; images and large files count toward that cap far more than text, so a chat with many of them can hit it well before the context indicator looks full, and Abundly shows This chat is too large to continue. In both cases retrying won’t help, because the same history is sent again, and the chat stays blocked even if you pick a different model. The new chat you start from the summary can use any model, including one with a larger context window.How to resolve: click New chat with summary on the message. The agent writes a handoff recap of the conversation and opens a fresh chat with it, so you can pick up where you left off. See Chat for how the summary flow works.If the new chat’s very first message is rejected the same way, another summary won’t help. The recap carries over a few of the most recent messages, and when those include large images or files they can exceed the request cap on their own. Start a plain + New Chat from the sidebar and share only the files you still need.
The model itself declined to answer — typically because the request tripped the provider’s content or safety rules. The agent’s reply is replaced by a Request refused card, and sending the same message again gives the same result, so there is no Try again button.How to resolve: use Edit on your last message to rephrase it, then send it again. Switching to a different model can also help, since providers draw these lines differently. See Model Selection for details.If the agent is exposed over HTTP, the same refusal is returned as status 422 — see API Access.
If an integration isn’t behaving as expected, check these common issues:
  1. Missing permissions — Ensure you’ve granted all required scopes/permissions during setup. Some integrations need specific OAuth scopes to access certain features.
  2. Not invited — For Slack, you need to /invite @YourAgent to each channel where you want it to work. The agent can only see channels it’s been invited to.
  3. Webhook not configured — For integrations that listen for events (like GitHub webhooks or Trello board events), ensure the webhook URL is set correctly in the external service.
  4. Token expired — Some OAuth tokens expire. For Google Drive, you can reconnect the token in place from the capability card or your Personal Tokens page — no need to reconfigure your agents. For other integrations, try disconnecting and reconnecting.
  5. Rate limits — External services may throttle requests. If you’re making many API calls, the service might temporarily block requests.
Each integration page has a troubleshooting section with specific guidance. See Integrations Overview for the full list.
This usually means the code is no longer valid.How verification codes work:
  • Each code expires 30 minutes after it is sent
  • You can have multiple active codes from recent requests
  • If you request many codes in a row, older active codes may be invalidated
  • You can request at most five codes per hour for the same email — after that, wait or use a code you already received
  • After five wrong guesses, your active codes are invalidated — request a new code
  • After you sign in successfully, all remaining active codes are invalidated
How to resolve:
  1. Use one of your most recently received codes
  2. Confirm the code is less than 30 minutes old
  3. Enter the code carefully to avoid typos
  4. If none work, request a fresh code and use it right away

​
Learn more

Agent Optimization

Reduce costs and improve performance

Integrations

Set up and configure external services

Model Selection

Choose the right AI model for your agent