Browser sessions let your agents interact with websites. When issues arise, here's how to diagnose and resolve them.
Login Sessions Expiring
Websites eventually expire login sessions for security reasons. When this happens, your agent will need to log in again.
Signs:
- Your agent reports being "logged out" or "session expired"
- Tasks that worked before now fail at authentication
- The agent asks for credentials that were already provided
Solutions:
- Your agent will usually handle re-authentication automatically if credentials are stored
- If the automatic login fails, check that the stored credentials are still valid
- For sites that changed their login flow, your agent might need guidance on the new process
CAPTCHAs and Security Challenges
Some websites present CAPTCHAs or security challenges to verify human users. Your agent can often solve these, but not always.
What helps:
- O-mega handles common CAPTCHA types automatically
- For persistent challenges, the website might be rate-limiting. Wait and try again later
- Some sites are more aggressive about detecting automation. Your agent adapts, but occasional failures happen
Bot Detection
Websites sometimes block automated access. Your agent uses various techniques to avoid detection, but some sites are stricter than others.
If a site seems to block your agent:
- Wait before retrying (the site might cool down)
- Try simpler tasks first to establish a browsing history
- Some sites may require different approaches—your agent will adapt
Manual Browser Takeover
When automation hits a wall, you can take over manually. During a browser session, use the takeover feature to:
- Complete complex CAPTCHAs your agent couldn't solve
- Navigate unusual login flows
- Handle multi-factor authentication that requires your device
Once you've completed the tricky part, return control to your agent to continue the work.
See Manual Browser Takeover for details.
Slow or Unresponsive Websites
Sometimes the target website is slow or having issues. Your agent will wait and retry, but external site problems are outside O-mega's control.
What to check:
- Is the website working when you access it directly?
- Are there known outages for that service?
- Is the site under heavy load?
If the site itself is having problems, wait until it's stable.
Session Limits
Browser sessions have time limits to prevent runaway operations. If a task is taking unusually long, the session might time out.
If sessions keep timing out:
- Break the task into smaller pieces
- Ensure the target site isn't unusually slow
- Check that there aren't infinite loops or stuck states
Clearing Browser Profiles
Browser profiles preserve login sessions across uses. If a profile becomes corrupted or problematic:
- Disconnect the relevant account from your agent
- Reconnect it
- This creates a fresh profile while preserving your credentials
The next session will need to log in fresh, but subsequent sessions will persist normally.
Specific Site Issues
Different sites behave differently. What works on one platform might not work identically on another. Your agent adapts to each site's quirks, but occasionally sites update their interfaces in ways that break existing patterns.
If a specific site suddenly stops working:
- Check if the site redesigned recently
- Try the operation manually to see what changed
- The system updates to handle site changes, but there can be a lag
Getting Help
For persistent browser issues:
- Note which site and what operation was attempted
- Describe what error or behavior you observed
- Contact support@o-mega.ai with these details
Related: Browser Sessions Overview | Browser Profiles | Manual Browser Takeover