Why Did My Test Stop Early?
Rihario explorations can stop early for several reasons: hit a blocker (CAPTCHA, MFA), detected an infinite loop, reached time limit, or was manually cancelled. The test results will show why it stopped. Most common reasons are blockers or time limits.
Common Reasons Tests Stop Early
1. Blocker Encountered
Most common reason: Hit something that blocks automation:
- CAPTCHA - Cannot solve CAPTCHAs automatically
- MFA prompt - Multi-factor authentication required
- Login required - Authentication needed
- Cookie banner - Complex cookie banner couldn't be dismissed
Status: BLOCKED
Solution: Take control manually, handle blocker, then resume
2. Time Limit Reached
Exploration took too long:
- Maximum duration - Exploration exceeded time limit
- Complex site - Site has many pages or complex flows
- Slow performance - Site is slow to load or respond
Status: TIMEOUT
Solution: Results up to timeout are saved; try focusing exploration with instructions
3. Infinite Loop Detected
Safety guard triggered:
- Redirect loop - Pages redirecting in circles
- Repeated actions - Same action performed multiple times
- Stuck state - Exploration stuck on same page
Status: STOPPED (loop detected)
Solution: This may indicate a bug in your app - check redirect logic
4. Manual Cancellation
You cancelled the test:
- Clicked cancel - Manually stopped exploration
- Closed browser - Navigation away stopped test
Status: CANCELLED
Solution: Start new exploration if needed
5. Error Occurred
Fatal error during exploration:
- Browser crash - Browser encountered fatal error
- Network failure - Connection issues
- System error - Unexpected technical problem
Status: ERROR
Solution: Try running again; contact support if persists
How to Check Why It Stopped
Check Test Results
In the test results, look for:
- Status - BLOCKED, TIMEOUT, STOPPED, CANCELLED, ERROR
- Last step - What was happening when it stopped
- Reason - Explanation of why it stopped
- Evidence - Screenshot or logs showing the issue
Review Test Logs
Check the step-by-step log:
- See last action taken
- Check for errors or warnings
- Review screenshot of final state
What to Do
If BLOCKED
- Take control manually
- Handle the blocker (solve CAPTCHA, authenticate, etc.)
- Resume exploration
- Or use test environment without blockers
If TIMEOUT
- Review results up to timeout (they're saved)
- Try focusing exploration with specific instructions
- Test smaller sections of your site
- Check if site performance is slow
If LOOP DETECTED
- This may indicate a bug in your app
- Check redirect logic
- Fix the loop in your app
- Re-run exploration
If ERROR
- Try running again
- Check if issue persists
- Contact support if problem continues
Preventing Early Stops
- Use test environments - Disable CAPTCHAs, MFA in staging
- Pre-authenticate - Log in manually before starting
- Focus instructions - Provide specific guidance for AI
- Test smaller sections - Break large sites into smaller explorations
- Monitor performance - Ensure site is fast and responsive
Getting Complete Results
Even if test stops early:
- Results are saved - Everything up to stop point is recorded
- Issues found - Problems detected before stop are reported
- Evidence captured - Screenshots and logs up to stop are available
Answer: Check Status and Reason
Check the test status and reason in the results. Most common reasons are blockers (CAPTCHA, MFA) or time limits. Review the last step and evidence to understand why it stopped, then take appropriate action.