Overview
This guide covers the most common issues users encounter when working with Enigma, along with detailed solutions and preventive measures.Session Issues
Session Stuck in Pending State
Symptoms:- Session status remains
pendingindefinitely - Session never transitions to
activestate - No browser instance appears to be assigned
- No available browser instances
- System experiencing high load
- Network connectivity issues
- Resource allocation bottleneck
-
Wait and Check Status
-
Terminate and Recreate
-
Check System Status
- Visit status.enigma.click
- Look for ongoing incidents or maintenance
- Check response times and success rates
-
Contact Support
- If issue persists for > 2 minutes
- Provide session ID and timestamp
- Include error logs if available
- Implement timeout logic when creating sessions
- Use retry logic with exponential backoff
- Monitor system status before critical operations
Tasks Timing Out
Symptoms:- Tasks return
TASK_TIMEOUTerror - Tasks exceed
maxDurationlimit - Incomplete results with timeout message
- Complex pages with heavy JavaScript
- Slow network connections
- Task requires multiple page loads
- Website has anti-bot protections
- Task instructions too complex
-
Increase Maximum Duration
-
Break Down Complex Tasks
-
Use Starting URL
-
Optimize Task Instructions
- Set realistic
maxDurationbased on task complexity - Test tasks on fast network first
- Monitor task execution times
- Keep task instructions specific and focused
Tasks Completing But No Result Returned
Symptoms:- Polling returns
pending: trueindefinitely - Task appears stuck even though browser finished
- No error message returned
- Task is still genuinely running
- Network issue between browser instance and API
- Result notification was lost
- WebSocket connection dropped
-
Continue Polling with Timeout
-
Check WebSocket Events
-
Terminate and Retry
- Use WebSocket for real-time updates
- Implement robust polling with timeouts
- Monitor both polling and WebSocket channels
Cost & Performance Issues
High Token Usage / Unexpected Costs
Symptoms:- Tasks consuming more tokens than expected
- Costs higher than estimated
usageobject shows large token counts
- Complex pages with lots of DOM elements
- Multiple failed attempts and retries
- Long-running tasks with many interactions
- Not using token limits
- Navigation to unnecessary pages
-
Set Token Limits
-
Use Starting URL
-
Block Unnecessary Domains
-
Simplify Task Instructions
-
Monitor Usage
- Always set
maxInputTokensandmaxOutputTokens - Use
startingUrlwhen possible - Block ad networks and analytics domains
- Keep tasks focused and specific
- Test on simple pages first
Guardrails & Interaction Issues
Guardrails Triggering Unexpectedly
Symptoms:- Agent frequently asks for input
- Tasks pause for user confirmation
guardrail_triggerevents fire often
- Task instructions are ambiguous
- Website requires login/authentication
- CAPTCHA or security check encountered
- Agent uncertain about next action
- Multiple valid options available
-
Make Instructions More Specific
-
Provide Credentials Upfront
-
Handle Guardrails Programmatically
-
Avoid Sites Requiring Auth
- Write clear, unambiguous task instructions
- Provide all necessary information upfront
- Test tasks on public pages first
- Handle common guardrail scenarios programmatically
Streaming & Connection Issues
Video Stream Not Loading
Symptoms:- Streaming endpoint returns errors
- Video player shows no content
- Connection timeout on stream URL
- Session not active yet
- Invalid session ID
- Network/firewall blocking WebRTC
- Browser instance crashed
-
Verify Session is Active
-
Check Network Configuration
-
Use Alternative Streaming Methods
WebSocket Connection Issues
Symptoms:- WebSocket fails to connect
- Connection drops frequently
- Events not received
- Invalid API key or session ID
- Firewall blocking WebSocket connections
- Network instability
- Session expired
-
Implement Reconnection Logic
-
Fall Back to Polling
- Implement automatic reconnection
- Have polling fallback ready
- Monitor connection health
- Use heartbeat/ping messages
Polling Not Working
Symptoms:- Polling requests return 404
- Task ID not recognized
- No updates on task status
- Incorrect task ID or session ID
- Task already completed and cleaned up
- Session expired
- Network request failing
-
Verify IDs are Correct
-
Handle Errors Gracefully
-
Check Session is Still Active
- Store IDs immediately when created
- Validate IDs before polling
- Check session status first
- Handle 404 errors gracefully
CAPTCHA & Security Challenges
CAPTCHA Blocking Tasks
Symptoms:- Tasks fail at CAPTCHA pages
- Agent cannot proceed past security checks
- Guardrail triggers asking how to handle CAPTCHA
- Website uses bot detection
- High security on target site
- Rate limiting triggered CAPTCHA
- IP address flagged
-
Manual Intervention via Guardrails
-
Use Manual Takeover
-
Avoid CAPTCHA-Heavy Sites
-
Rate Limit Your Requests
- Use manual takeover mode when CAPTCHAs expected
- Rate limit requests to avoid triggering security
- Test target sites beforehand
- Have fallback strategy for CAPTCHA sites
Debugging Tips
Enable Verbose Logging
Monitor All Events
Quick Reference
| Issue | First Thing to Try | Documentation |
|---|---|---|
| Session pending too long | Wait 30s, then terminate & recreate | Sessions |
| Task timeout | Increase maxDuration or simplify task | Tasks |
| High costs | Set maxInputTokens and maxOutputTokens | Cost Optimization |
| Guardrails firing | Make instructions more specific | Guardrails |
| Stream not loading | Verify session is active | Streaming |
| WebSocket failing | Implement polling fallback | Events |
| CAPTCHA blocking | Use manual takeover mode | Manual Control |