Why Some Steps Are Skipped or Blocked

Rihario marks steps as SKIPPED or BLOCKED when the AI cannot proceed. SKIPPED means the step was intentionally skipped for safety or efficiency. BLOCKED means exploration hit an insurmountable obstacle. Understanding these statuses helps you interpret results correctly.

SKIPPED Steps

Steps are marked as SKIPPED when:

Safety Guards Trigger

• Infinite loop detected - Same page loaded multiple times without progress
• Redirect loop - Endless redirects detected
• Time limit reached - Action taking too long, skipped to prevent hanging
• Retry limit exceeded - Failed multiple times, giving up

Efficiency Optimizations

• Similar actions already performed - Already clicked similar buttons, skipping duplicates
• Low-value exploration - Element doesn't add value to exploration
• Already explored - Page or flow already checked

Example: SKIPPED Step

BLOCKED Steps

Steps are marked as BLOCKED when:

1. CAPTCHA Encountered

The AI cannot solve CAPTCHAs. When encountered:

• Exploration stops
• Status marked as BLOCKED
• Reason: "CAPTCHA detected"
• You can take control to solve manually

2. Multi-Factor Authentication (MFA)

MFA prompts require human input:

• Exploration stops
• Status marked as BLOCKED
• Reason: "MFA prompt detected"
• You can authenticate manually, then resume

3. Cookie Banner That Can't Be Dismissed

Some cookie banners cannot be auto-dismissed:

• Custom implementations not recognized
• Complex multi-step consent flows
• Banners that block all interaction
• Exploration marked as BLOCKED
• You can dismiss manually, then resume

4. Authentication Required

Protected pages that require login:

• No valid session
• Login prompt encountered
• Exploration may be BLOCKED or paused
• You can authenticate manually

5. Age Verification or Paywall

Content gates that block access:

• Age verification screens
• Subscription paywalls
• Payment required screens
• Exploration marked as BLOCKED

Example: BLOCKED Step

FAILED vs BLOCKED

It's important to distinguish:

• FAILED - Something broke (JavaScript error, network failure, etc.)
• BLOCKED - Hit an intentional blocker (CAPTCHA, MFA, etc.)

BLOCKED isn't necessarily a problem with your app - it's an intentional security measure that prevents automation. FAILED indicates an actual problem.

See What FAILED vs BLOCKED vs SKIPPED Means for detailed comparison.

How to Handle Blockers

Option 1: Take Control

1. Pause the exploration when it gets blocked
2. Click "Take Control"
3. Handle the blocker manually (solve CAPTCHA, authenticate, etc.)
4. Resume exploration
5. AI continues from where you left off

Option 2: Start from Different State

If blockers are consistent:

• Authenticate manually first (in your browser)
• Start exploration from an already-authenticated page
• Avoid the blocker entirely

Option 3: Use Test Environment

For testing:

• Disable CAPTCHAs in staging/test environments
• Use test accounts without MFA
• Remove paywalls or age gates in test environments
• Then run Rihario on the test environment

Common Blocker Scenarios

Scenario 1: Contact Form with CAPTCHA

Scenario 2: Login Flow with MFA

Preventing Blockers

To minimize blockers:

• Use staging environments - Disable CAPTCHAs and MFA in test environments
• Test accounts - Create accounts specifically for testing
• Manual pre-auth - Authenticate manually before starting exploration
• White-list IPs - If possible, whitelist Rihario servers

Next Steps

• Learn the difference between FAILED and BLOCKED
• See how cookie banners are handled
• Understand CAPTCHA and MFA limitations