Chat Issues
"API key not configured" or no response
Your OpenRouter API key is missing or invalid.
- Go to Settings → LLM Provider
- Make sure OpenRouter is selected
- Enter a valid API key starting with
sk-or-v1-... - Click Save Key
To confirm the key works, open Settings → Diagnostics: the LLM API Key row tests the provider currently selected in Settings and names the model it checked. A valid key passes on every provider, not only OpenRouter.
"LLM API error: 400"
The model you are using may not support tool calling or has a formatting issue.
- Go to Settings → AI Model
- Switch to a different model
- Recommended: any model from the OpenRouter recommended list
"LLM API error: 429"
You have hit your OpenRouter rate limit.
- Free models have daily usage limits on OpenRouter
- Adding a small amount of credit to your OpenRouter account raises the limit
- Or switch to a different free model temporarily
"LLM API error: 524"
Cloudflare timeout — the model took too long to respond (over 100 seconds). This usually happens with local models over a Cloudflare Tunnel.
- Switch to a smaller, faster model
- Use a cloud-based model via OpenRouter instead
Responses are slow
- Complex queries involving multiple tools (email + calendar + web search) can take 20-60 seconds — this is normal
- Switch to a faster model in Settings
- Disable unused integrations
Google Workspace Issues
"Google not connected" or tools not working
- Go to Settings → Google Workspace
- Click Re-authorize to reconnect
- Complete the Google sign-in flow
"Access blocked" when connecting Google
Your Google Cloud app may be in testing mode. Fix:
- Go to console.cloud.google.com
- Navigate to APIs & Services → OAuth consent screen
- Under Test users, add your email address
- Try connecting again
Google APIs not working
Make sure all required APIs are enabled in your Google Cloud project:
- Gmail API
- Google Calendar API
- Google Drive API
- Google Tasks API
Go to APIs & Services → Library to enable them.
Microsoft 365 Issues
"Microsoft not connected" or tools not working
- Go to Settings → Microsoft 365
- Click Re-authorize to reconnect
- Complete the Microsoft sign-in flow
"Admin approval required"
Your organization's IT policy requires approval for new apps.
- Contact your IT administrator to approve the app in Azure Portal → Enterprise Applications
- Or use a personal Microsoft account instead of a work account
"Invalid client secret"
Your client secret may have expired or been copied incorrectly.
- Go to portal.azure.com
- Navigate to your app registration → Certificates & secrets
- Create a new client secret
- Update it in AIDA Settings → Microsoft 365
Web Search Issues
"Search not configured"
- Go to Settings → Web Search
- Select a provider (Tavily recommended)
- Enter your API key
- Click Save then Test Search
"Invalid API key"
Your search API key may have been copied incorrectly. Generate a new one from your provider's dashboard.
Telegram Issues
Bot not responding
- Verify the token in Settings → Telegram Bot is correct
- Make sure AIDA was restarted after saving the token
- Check that AIDA is running:
sudo docker ps
Morning briefing not sending
- Verify briefing is enabled in Settings → Morning Briefing
- Check your timezone is set correctly in Settings → User Profile
- Make sure Telegram channel is selected in briefing settings
Local AI Issues
"Connection refused" when using Ollama
Ollama is not running. Start it with the AIDA launcher:
- Windows: Double-click
start-aida-local.bat - Mac/Linux: Run
start-aida-local.sh
"524 timeout" with local models
The model is too slow for the Cloudflare Tunnel timeout limit.
- Use a smaller model —
qwen2.5:0.5bis the fastest - Enable GPU acceleration if your machine has a GPU
Tunnel URL not working
The Cloudflare Tunnel URL changes every time the launcher restarts. Update the URL in Settings → Ollama → Server URL after each restart.
Account and License Issues
Trial expired
Your 7-day trial has ended. Purchase a license at autafy.ca and enter the key when prompted.
"Invalid license key"
Make sure you copied the full key including the AIDA- prefix. Contact support at autafy.ca if the issue persists.
Still having issues?
Visit autafy.ca for support or contact us directly.