Skip to main content
When a task cannot open a website or returns incomplete data, diagnose the page before changing settings. Capture the final URL, error text, screenshot, time, task environment, and several output rows. That evidence separates access failures from task-design or data-quality issues.

​
Diagnose the issue

​
Test one change at a time

  1. Reproduce the issue with a small, representative scope.
  2. Identify the first unexpected page state or failed action.
  3. Change one relevant setting only.
  4. Re-test the same scope and compare screenshot, final URL, fields, and record count.
  5. Keep the change only when the result is reproducible; otherwise revert it and inspect the next likely cause.

​
When to stop and contact support

Stop the run when a small, controlled test still returns an access, CAPTCHA, or login page. Also stop when retries add cost but do not return valid data. When you contact Support, include:
  • Whether the run was Local or Cloud, and when it ran
  • The target URL and error message
  • A screenshot and the relevant event-log excerpt, with secrets removed
  • What you expected to happen and what happened instead