← Back to Documentation
🔧

Troubleshooting

Solutions to common issues you might encounter.

Google Connector Issues

"Access blocked: This app's request is invalid"

This usually means the redirect URI doesn't match. Make sure the redirect URI in Sontairo matches exactly what you configured in the Google Cloud Console (including the protocol — http vs https).

"Error 403: access_denied"

Your app is likely in testing mode. Go to the Google Cloud Console → OAuth consent screen → Test users, and add the Google account you're trying to authorize.

"This app isn't verified" warning

This is normal for apps in testing mode. Click AdvancedGo to [app name] (unsafe)to proceed. For production use, submit your app for Google verification.

Provider Issues

AI responses are generic / not using agent persona

Make sure you've selected a specific agent in the chat dropdown (not "General"). Check that the agent has a custom system prompt set. The AI adopts the agent's persona only when a system prompt is configured.

Auto-generate agent details fails

The auto-generate feature tries all active providers in sequence. Make sure you have at least one active provider key configured. Go to Providers and verify a key is active.

Tools not working in chat

Tools use native function calling. Some older or smaller models may not support function calling well. Try switching to a more capable model (e.g., GPT-4, Claude 3, Gemini Pro) in the provider settings.

Connector Issues

Connector stuck in "Pending" status

Click the Configure button on the connector card and enter the required credentials. The connector will switch to "Active" once credentials are saved.

Slack bot not responding

Verify that your bot token starts with xoxb- (not xoxp-). Make sure the bot has been invited to the channel you specified in the Channel ID field.

General Issues

Agent Network graph not showing agents

The graph requires at least one agent to display. Create an agent using the Create Agent button below the graph, or ask the AI to create one via chat.

Cron jobs not running

Cron jobs require a background worker process to be running. Make sure the worker is configured and running in your deployment. Check that the cron job is set to "Active" (not paused).

Still stuck? Open an issue on the GitHub repository.