Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.abundly.ai/llms.txt

Use this file to discover all available pages before exploring further.

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.
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
  • 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