Scheduling & Automation

SnowScrape allows you to schedule jobs to run automatically at specific times. This is perfect for monitoring prices, tracking inventory, or collecting data at regular intervals.

Schedule Configuration

Schedules are defined using three components:

Common Schedule Examples

{
  "days": [0, 1, 2, 3, 4, 5, 6],
  "hours": [9],
  "minutes": [0]
}

{
  "days": [1, 2, 3, 4, 5],
  "hours": [18],
  "minutes": [0]
}

{
  "days": [0, 1, 2, 3, 4, 5, 6],
  "hours": [0, 6, 12, 18],
  "minutes": [0]
}

{
  "days": [0, 1, 2, 3, 4, 5, 6],
  "hours": [9, 17],
  "minutes": [0]
}

Timezone

All schedules run in UTC timezone. When setting up schedules, convert your local time to UTC. For example:

• 9 AM EST = 14:00 UTC (hours: [14])
• 6 PM PST = 02:00 UTC next day (hours: [2])
• 12 PM GMT = 12:00 UTC (hours: [12])

Managing Scheduled Jobs

Pausing Schedules

Pause a job to temporarily stop scheduled runs without deleting the configuration. The job will remain paused until you resume it.

Manual Triggers

You can always run a scheduled job manually using the "Run Now" button. This doesn't affect the schedule - the job will still run at its next scheduled time.

Overlapping Runs

If a previous run is still executing when the next scheduled time arrives, SnowScrape will skip the new run and wait for the next scheduled time. This prevents duplicate data and excessive resource usage.

Best Practices

• Match your data freshness needs- Don't scrape hourly if daily is sufficient
• Consider target site load - Avoid peak hours for better success rates
• Set up alerts - Configure webhooks to know when scheduled jobs fail
• Test first - Run a job manually to verify it works before scheduling
• Monitor costs - Frequent schedules increase API usage

Next Steps