When your agent connects to external services—email providers, calendar systems, business tools—occasional connection issues can occur. Here's how to diagnose and fix them.
Expired Connections
Third-party services eventually expire their authorization tokens. When this happens, your agent loses access to that service until you reconnect.
Signs:
- Your agent reports it can't access a previously working service
- Tasks fail with "authorization" or "permission" errors
- You see prompts to reconnect or reauthorize
Solution:
- Go to your agent's settings and find the connected tools or accounts section
- Disconnect the affected service
- Reconnect by going through the authorization flow again
This refreshes the connection with new credentials.
Authorization Failures
Sometimes the initial connection to a service doesn't complete successfully.
Common causes:
- You closed the authorization window before finishing
- The service was temporarily unavailable
- Your account on the external service has restrictions
What to do:
- Try connecting again, making sure to complete the full authorization flow
- Check that your account on the external service is in good standing
- Verify you're authorizing the correct account (personal vs. work, etc.)
Service Outages
External services occasionally have outages. When a connected service is down, your agent can't interact with it.
How to check:
- Try accessing the service directly (in your browser)
- Check the service's status page
- Look for reports of widespread issues
If the service itself is down, wait until it recovers. Your agent will work normally once the service is back.
Permission Changes
If you changed permissions on the external service—revoked access, changed scopes, updated security settings—your agent might lose its connection.
Solution:
- Reconnect the service
- Make sure to grant all the permissions your agent needs
- Some services require periodic reauthorization as a security measure
Rate Limiting
External services limit how many requests you can make. If your agent makes many requests quickly, the service might temporarily block access.
Signs:
- "Too many requests" or "rate limited" errors
- Operations that work individually fail when done in bulk
- Intermittent failures that resolve after waiting
What to do:
- Wait a few minutes before retrying
- For bulk operations, consider spacing them out
- The agent usually handles rate limits automatically by backing off and retrying
Wrong Account Connected
Sometimes you might have connected the wrong account (personal instead of work, test instead of production).
Solution:
- Disconnect the current connection
- When reconnecting, make sure you're logged into the correct account on the external service
- Some services allow multiple accounts—check which one is active
Firewall or Network Issues
In some corporate environments, firewalls or network policies might block connections to external services.
Signs:
- Connections work on personal networks but fail on corporate networks
- Timeout errors when trying to connect
- Security software warnings
What to check:
- Ask your IT department if the service is allowed
- Try from a different network
- Some organizations require special configuration for third-party integrations
Reconnecting Multiple Services
If several integrations stop working at once, it might be an account-level issue rather than individual service problems.
What to check:
- Is your O-mega account active?
- Are there billing issues?
- Has your organization's policy changed?
For widespread connection issues, contact support@o-mega.ai.
When to Contact Support
Reach out if:
- You've tried reconnecting multiple times without success
- The error messages don't make sense
- The issue affects multiple users in your organization
- You suspect a security issue
Include details about which service, what error you saw, and what you've already tried.
Related: Agent Accounts | What Makes Up an Agent