001 / DOCS
Scheduling
Schedule automatic fetches with WP-Cron in Ingestics.
Setting up a schedule
- Open a provider in Ingestics
- Go to the Schedule tab
- Select an interval (available intervals depend on your edition)
- Save the provider
Ingestics uses WordPress’s built-in WP-Cron system. No external cron job is required, but you can improve reliability by disabling WP-Cron and setting up a real cron job.
Available intervals by edition
| Edition | Intervals | API/RSS |
|---|---|---|
| Free | Manual only | — |
| Lite ($49) | 2h, 4h, 6h | Combined rotation |
| Pro ($99) | 12h + custom intervals | Shared rotation |
| Business ($199) | All intervals | Independent API and RSS schedules |
Custom intervals (Pro+)
On the Pro edition and above, you can define custom intervals. For example, you can fetch from a specific provider every 30 minutes while keeping others at 6 hours. This is useful when different APIs have different update frequencies.
Independent API/RSS schedules (Business)
On the Business edition, API and RSS fetches run on independent schedules. This means API fetches do not block RSS fetches, and vice versa. This improves throughput when you have many providers.
Provider rotation
When multiple providers share a schedule slot, Ingestics rotates through them:
- Lite — Combined rotation. API and RSS providers share the same schedule slot.
- Pro — Shared rotation. Providers share schedule slots but with more granular control.
- Business — Full control. Each provider can have its own independent schedule.
Improving WP-Cron reliability
WordPress’s built-in WP-Cron relies on site visitors to trigger scheduled tasks. On low-traffic sites, this can cause delays. To improve reliability:
- Disable WP-Cron in
wp-config.php:define('DISABLE_WP_CRON', true); - Set up a real cron job on your server that hits
wp-cron.phpevery minute:
* * * * * wget -q -O - https://yoursite.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1This ensures scheduled fetches run exactly on time, regardless of site traffic.
Rate limiting
Ingestics includes built-in rate limiting to avoid overwhelming external APIs:
- Requests are spaced out with delays between fetches
- On the Business edition, a rate-limit budget queue manages request frequency across all providers
- Exponential backoff is used when APIs return 429 (Too Many Requests) responses
Viewing scheduled tasks
To see when your providers are scheduled to fetch next:
- Go to Ingestics → Dashboard
- View the “Next Scheduled Fetch” column for each provider
- Or open individual providers and check the Schedule tab
Start automating.
Download Ingestics free. Start fetching APIs and RSS feeds in minutes.