> ## Documentation Index
> Fetch the complete documentation index at: https://www.octoparse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Logs & event tracking

> Use task events, screenshots, and output checks to diagnose Octoparse access failures and verify a recovery.

Logs and event tracking help you understand what happened during a task run. Use them with page screenshots and a sample of output data to troubleshoot failed runs, incomplete data, unexpected stops, login problems, proxy or User-Agent changes, verification events, and Cloud-run behavior.

## 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:

| Situation | Why logs help |
| - | - |
| A task fails | Identify the step or page where it failed |
| Data is missing | Check whether extraction fields were reached |
| Fewer records than expected | Review pagination, loops, or stopping conditions |
| Cloud runs behave differently | Compare cloud behavior with local tests |
| A scheduled task stops | Check run history and failure timing |

## Troubleshooting workflow

<Steps>
  <Step title="Find the failed or incomplete run">
    Open the task's run history and select the run you want to inspect.
  </Step>

  <Step title="Review the timeline">
    Look for the first warning, failed action, proxy or User-Agent change, timeout, verification event, or unexpected stop.
  </Step>

  <Step title="Compare with the workflow">
    Match the log event to the corresponding action in the task.
  </Step>

  <Step title="Adjust the task">
    Update waits, selectors, pagination, login, cookies, [proxy](/docs/en/platform/proxy), or extraction settings as needed.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## 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](/docs/en/platform/local-vs-cloud) 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.

<Note>
  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.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.