Quick debugging checklist

Key artifacts to check:
screenshot_final— Final page staterecording— Video of what happenedllm_response_parsed— What the AI decided to dovisible_elements_tree— What elements were detectedhar— Network requests if something failed to load
Step 1: Check the run
| Status | What it means | Likely cause |
|---|---|---|
completed | Run finished, but output may be wrong | Prompt interpretation issue |
failed | System error | Browser crash, network failure |
terminated | AI gave up | Login blocked, CAPTCHA, page unavailable |
timed_out | Exceeded max_steps | Task too complex, or AI got stuck |
canceled | Manually stopped | — |
Step 2: Read the step timeline
The timeline shows each block and action in execution order.Step 3: Inspect artifacts
Common issues and fixes
Run Status Issues
Run completed but output is wrong
Run completed but output is wrong
Symptom: Status is
completed, but the extracted data is incorrect or incomplete.Check: screenshot_final (right page?) and llm_response_parsed (right elements?)Fix:- Add specific descriptions in your schema:
"description": "The price in USD, without currency symbol" - Add visual hints: “The price is displayed in bold below the product title”
Run timed out
Run timed out
Symptom: Status is
timed_out.Check: recording (stuck in a loop?) and step_count (how many steps?)Fix:- Increase
max_stepsif the task genuinely needs more steps - Add explicit completion criteria: “COMPLETE when you see ‘Order confirmed’”
- Break complex tasks into multiple workflow blocks
Run stuck in queued state
Run stuck in queued state
Symptom: Run stays in
queued status and never starts.Likely causes: Concurrency limit hit, sequential run lock, or high platform load.Fix:- Wait for other runs to complete
- Check your plan’s concurrency limits in Settings
- If using “Run Sequentially” with credentials, ensure prior runs finish
504 Gateway Timeout on browser session
504 Gateway Timeout on browser session
Symptom: Getting
504 Gateway Timeout errors when creating browser sessions.Fix:- Retry after a few seconds — usually transient
- For self-hosted: check infrastructure resources
- If persistent, contact support with your run IDs
Element & Interaction Issues
AI clicked the wrong element
AI clicked the wrong element
Symptom: Recording shows the AI clicking something other than intended.Check:
visible_elements_tree (element detected?) and llm_prompt (target described clearly?)Fix:- Add distinguishing details: “Click the blue Submit button at the bottom of the form”
- Reference surrounding text: “Click Download in the row that says ‘January 2024’”
Element not found
Element not found
Symptom:
failure_reason mentions an element couldn’t be found.Check: screenshot_final (element visible?) and visible_elements_tree (element detected?)Likely causes: Dynamic loading, iframe, below the fold, unusual rendering (canvas, shadow DOM)Fix:- Add
max_screenshot_scrollsto capture lazy-loaded content - Describe elements visually rather than by technical properties
- Add wait or scroll instructions in your prompt
Date fields entering wrong values
Date fields entering wrong values
Symptom: Dates entered in wrong format (MM/DD vs DD/MM) or wrong date entirely.Check:
recording (how did AI interact with the date picker?)Fix:- Specify exact format: “Enter the date as 15/01/2024 (DD/MM/YYYY format)”
- For date pickers: “Click the date field, then select January 15, 2024 from the calendar”
- If site auto-formats: “Type 01152024 and let the field format it”
Address autocomplete cycling or wrong selection
Address autocomplete cycling or wrong selection
Symptom: AI keeps clicking through address suggestions in a loop, or selects wrong address.Check:
recording (is autocomplete dropdown appearing?)Fix:- Specify selection: “Type ‘123 Main St’ and select the first suggestion showing ‘New York, NY’”
- Disable autocomplete: “Type the full address without using autocomplete suggestions”
- Break into steps: “Enter street address, wait for dropdown, select the matching suggestion”
Authentication Issues
Login failed
Login failed
Symptom: Status is
terminated with login-related failure reason.Check: screenshot_final (error message?) and recording (fields filled correctly?)Likely causes: Expired credentials, CAPTCHA, MFA required, automation detectedFix:- Verify credentials in your credential store
- Use
RESIDENTIAL_ISPproxy for more stable IPs - Configure TOTP if MFA is required
- Use a browser profile with an existing session
CAPTCHA blocked the run
CAPTCHA blocked the run
Symptom:
failure_reason mentions CAPTCHA.Fix options:- Browser profile — Use an authenticated session that skips login
- Human interaction block — Pause for manual CAPTCHA solving
- Different proxy — Use
RESIDENTIAL_ISPfor static IPs sites trust more
Data & Output Issues
AI hallucinating or inventing data
AI hallucinating or inventing data
Symptom: Extracted data contains information not on the page.Check:
screenshot_final (data visible?) and llm_response_parsed (what did AI claim to see?)Fix:- Add instruction: “Only extract data visibly displayed on the page. Return null if not found”
- Make schema fields optional where appropriate
- Add validation: “If price is not displayed, set price to null instead of guessing”
File downloads not working
File downloads not working
Symptom: Files download repeatedly, wrong files, or downloads don’t complete.Check:
recording (download button clicked correctly?) and downloaded_files in responseFix:- Be specific: “Click the PDF download button, not the Excel one”
- Add wait time: “Wait for the download to complete”
- For multi-step downloads: “Click Download, then select PDF format, then click Confirm”
Environment Issues
Site showing content in wrong language
Site showing content in wrong language
Symptom: Site displays in unexpected language based on proxy location.Check: What
proxy_location is being used? Does site geo-target?Fix:- Use appropriate proxy:
RESIDENTIAL_USfor English US sites - Add instruction: “If the site asks for language preference, select English”
- Set language in URL:
https://example.com/en/
Workflow gets stuck in a loop
Workflow gets stuck in a loop
Symptom: Recording shows AI repeating the same actions without progressing.Check:
recording (what pattern is repeating?) and conditional block exit conditionsFix:- Add termination: “STOP if you’ve attempted this action 3 times without success”
- Add completion markers: “COMPLETE when you see ‘Success’ message”
- Review loop conditions — ensure exit criteria are achievable
When to adjust prompts vs parameters
Adjust prompt
- AI misunderstood what to do
- Clicked wrong element
- Ambiguous completion criteria
- Extracted wrong data
Adjust parameters
- Timed out → increase
max_steps - Site blocked → change
proxy_location - Content didn’t load → increase
max_screenshot_scrolls
File a bug
- Visible element not detected
- Standard UI patterns don’t work
- Consistent wrong element despite clear prompts
Next steps
Using Artifacts
Detailed reference for all artifact types
Reliability Tips
Write prompts that fail less often

