Skip to main content
Find the symptom below, try the quick fix, and follow the link for the full guide. If Bizzy itself seems down, check status.bizzyco.ai before debugging your own setup.

​
Email & inbox

“Access denied” usually means your workspace blocks third-party apps — ask your IT administrator to approve Bizzy. An “invalid grant” error means the authorization expired: disconnect and reconnect the account. See Connect Email → Troubleshooting.
The initial sync can take a few minutes, and only emails from the last 30 days are synced. If a previously connected account stopped syncing, its token may have been revoked — reconnect it from the Email Addresses page. See Connect Email → Troubleshooting.

​
Domains & DNS

TXT records can take 5–30 minutes to propagate, and the record must be at _bizzy.<your-domain> — not on the apex. See Verify a Domain → Troubleshooting.
Sending reputation depends on your domain’s authentication records being verified and warmed up. See Deliverability.

​
Phone numbers

Your filters are probably too narrow or the area code is out of stock. Loosen the pattern, switch the type to Any, or try a nearby area code. See Buying a Number → Troubleshooting.
Check the number’s status on the Phone Numbers page — you’ll also get a “Connection lost” notification when a number goes offline. See Configuring Numbers.

​
Agents & automations

The file’s Agent access flag is probably off (it’s off by default for privacy), or indexing hasn’t finished — give it a minute after enabling. See Agent Access & RAG Indexing.
Check that the automation is Active (not paused, completed, or expired) and that its trigger matches the event. See Your First Automation → Troubleshooting.
You may have hit your monthly usage allowance — at the cutoff threshold, AI features pause until you buy credits, upgrade, or the billing cycle resets. Check Settings > Account > Billing. See Understanding Limits.

​
API & MCP

A 401 means the API key is missing or invalid; a 403 means the key lacks the permission scope for that endpoint. Check your key on the API Keys page. See Error Handling.
You’ve exceeded your plan’s per-minute request limit. Wait the number of seconds given by the Retry-After header, then retry. See Rate Limits for the limits on each plan.
Re-run the OAuth flow from your client and approve the consent screen — and make sure the client points at https://mcp.bizzyco.ai. See MCP Connection → Troubleshooting.
You’ve exceeded your plan’s per-minute MCP request limit. The HTTP response looks normal — the throttle is reported inside the JSON-RPC error, so wait data.retryAfter seconds before retrying. See MCP Rate Limits for the limits on each plan.

​
Still stuck?

For API issues, grab the X-Request-ID header from the failing response — it lets support find your exact request. See Getting Support for what else to include.

Getting Support

Contact the team with the right details

Service Status

Check for ongoing incidents
Last modified on August 9, 2026