Schedules let Octoparse run tasks automatically at defined times or intervals. They are useful for recurring data collection workflows such as price monitoring, lead list updates, inventory checks, or routine reporting. Scheduled runs are typically used with cloud extraction so tasks can run without depending on your local computer.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.
When to use schedules
Use schedules when:- The same data needs to be collected 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
Build and test the task
Confirm the task extracts the correct fields and handles pagination or detail pages correctly.
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 |
Recommended practices
- Test the task manually before scheduling it.
- Start with a conservative frequency.
- Monitor the first few scheduled runs.
- Use logs to diagnose failures.
- Review exported records for missing fields or duplicates.
- Adjust frequency if the website updates less often than expected.