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

# Schedules

> Schedule Octoparse tasks automatically and manage recurring cloud or local runs, runtime limits, frequency, and reliability.

Schedules let Octoparse run tasks automatically at defined times or intervals. They are useful for recurring data scraping workflows such as price monitoring, lead list updates, inventory checks, or routine reporting.

Octoparse supports scheduled runs in both [cloud and local](/docs/en/platform/local-vs-cloud). Cloud scheduling is recommended for most workflows because it runs without depending on your local computer. Local scheduling is available for cases where Cloud Extraction does not work or where the target website requires a local IP address for login or access.

## When to use schedules

Use schedules when:

* The same data needs to be scraped repeatedly
* You need daily, weekly, or hourly updates
* The task should run outside working hours
* Data needs to be ready before a report or downstream workflow
* You want to reduce manual task starts

## Scheduling workflow

<Steps>
  <Step title="Build and test the task">
    Confirm the task extracts the correct fields and handles pagination or detail pages correctly.
  </Step>

  <Step title="Choose the run environment">
    Use Cloud Extraction when the task should run without your computer. Use Local Extraction when it depends on your device, local network, local IP, or an active local session.
  </Step>

  <Step title="Set the schedule">
    Choose when and how often the task should run.
  </Step>

  <Step title="Configure export">
    Set up manual or automatic export depending on where the data should go.
  </Step>

  <Step title="Monitor results">
    Check run history, logs, and exported records after scheduled runs. For cloud-specific time zones, queues, overlaps, and failures, see [Schedule cloud runs](/docs/en/platform/cloud-schedules).
  </Step>
</Steps>

## What to check before scheduling

Before enabling a schedule, check:

| Check | Why it matters |
| - | - |
| Task stability | Scheduled runs repeat the same workflow automatically |
| Login/session setup | Expired sessions can cause failed runs |
| Cloud compatibility | Scheduled runs usually depend on cloud execution |
| Export settings | Data may need to be delivered automatically |
| Website rate limits | Frequent runs can increase blocking risk |
| Run time | Long tasks may overlap if scheduled too often |

## Limit the runtime of a scheduled local task

For a local schedule, set **Maximum runtime** to stop a task that remains active longer than expected. Enter the limit in whole minutes; enter `0` when the run should have no time limit.

The timer starts with the scheduled local run. When the limit is reached, Octoparse stops the task whether it is running or paused. This prevents a stalled or unusually slow task from occupying the local computer indefinitely and makes it easier to leave enough time before the next scheduled run.

<Note>
  Maximum runtime applies only to scheduled local extraction. It does not limit a manually started local run or a cloud run, and it does not guarantee that the task will finish collecting all intended data before the limit.
</Note>

## Recommended practices

* Test the task manually before scheduling it.
* Start with a conservative frequency.
* Monitor the first few scheduled runs.
* Use [logs](/docs/en/platform/logs-and-events) to diagnose failures.
* Review exported records for missing fields or duplicates.
* Adjust frequency if the website updates less often than expected.

<Warning>
  Avoid scheduling tasks more frequently than needed. Excessive runs can create duplicate data, increase usage, and raise the chance of website blocking.
</Warning>


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