Errors & Debugging
While we aim for 100% uptime, implementation errors can occur. Use this guide to identify HTTP status codes and troubleshoot common SDK issues.
API Status Codes
Standard HTTP codes returned by the AsroChat Edge API.
Unauthorized
Your API Key is missing, invalid, or has been revoked in the dashboard.
Recommended Fix:
Verify the 'apiKey' parameter in AsroChatSDK.init().
Payment Required
Your project has run out of monthly or top-up credits.
Recommended Fix:
Upgrade your plan or purchase a one-time credit top-up.
Forbidden
Domain whitelist violation. This key is restricted to another domain.
Recommended Fix:
Add your current domain to the whitelist in Dashboard > API Keys.
Bot Not Found
The 'botId' provided does not match any active bots in your account.
Recommended Fix:
Ensure you are using the correct Bot ID from the 'Bots' tab.
Payload Too Large
The training file you uploaded exceeds the 300KB size limit.
Recommended Fix:
Compress your document or split it into smaller files (Max 2 files).
Rate Limit Exceeded
You've sent too many requests in a short window (Burst limit).
Recommended Fix:
Wait 60 seconds or upgrade to a Pro plan for higher throughput.
Internal Server Error
The AI model or database is experiencing high latency.
Recommended Fix:
Check our status page or try again in a few minutes.
Gateway Timeout
The bot took too long to generate a specialized response.
Recommended Fix:
Simplify your RAG data structure to reduce ingestion lookups.
Common SDK Issues
Browser-side troubleshooting for the chat widget.
Widget Not Displaying
- 1. Ensure the SDK <script> is added before your init call.
- 2. Check the Browser Console for "403 Forbidden" errors (Domain lock).
- 3. Verify the container element (if custom) exists on the DOM.
Delayed Responses
- 1. Ingestion logic can slow down if your training data has messy formatting.
- 2. Large attachments (>200KB) take longer for the AI to vector-index initially.
- 3. Check your network tab for "504 Gateway Timeout" from the AI provider.
Still Not Working?
Our engineers are available via email for architectural or debugging help. Include your Bot ID and a link to the page where the error occurs.