What logs are for
Logs can help answer questions such as:- Did the task start successfully?
- Which step failed?
- Did the page load correctly?
- Did pagination continue as expected?
- Was a login or cookie state missing?
- Did the task extract records?
- Why did the cloud run stop?
When to check logs
Check logs when:Troubleshooting workflow
1
Find the failed or incomplete run
Open the task’s run history and select the run you want to inspect.
2
Review the timeline
Look for the first warning, failed action, proxy or User-Agent change, timeout, verification event, or unexpected stop.
3
Compare with the workflow
Match the log event to the corresponding action in the task.
4
Adjust the task
Update waits, selectors, pagination, login, cookies, proxy, or extraction settings as needed.
5
Run a sample again
Test the updated workflow before scheduling or scaling the task. Compare the final page, screenshot, and several output rows with the baseline.
Common causes of run issues
- Page structure changed
- Element selector no longer matches
- Content loaded too slowly
- Login session expired
- CAPTCHA or blocking appeared
- Pagination did not continue
- Cloud environment differs from local testing
- The task stopped before reaching all pages
Best practices
- Review logs after major task changes.
- Keep a successful run as a comparison point.
- Test locally when you need to observe page behavior directly.
- Use cloud logs when scheduled or unattended runs fail.
- Combine logs with data count and export status to confirm task health.
Logs show what happened during a run, but they may not always explain why a website behaved differently. Keep Cookies and credentials out of exported log excerpts and support tickets. For complex sites, compare Local tests, Cloud logs, screenshots, and the target page structure together.