How do I choose a sustainable refresh schedule?

Scheduling requires a connected source URL. The shortest supported interval is 60 minutes and the longest is seven days. Saved schedules are checked by the cloud runner while the browser is closed. A due time is a scheduling target, not a guarantee of exact-to-the-minute completion; inspect the next run and resulting job status.

Merchant includes 100 jobs per workspace per day. One hourly feed projects about 24 scheduled jobs per day; five hourly feeds would exceed the allowance before manual work. Choose an interval that reflects how often the source really changes and leaves capacity for imports, re-audits, checks, and retries. Freshness warnings are a separate threshold from the refresh interval.

What to do

1. Verify a successful manual refresh from the source URL.
2. Open the feed schedule and choose an interval and valid timezone.
3. Set a freshness warning appropriate to the source update pattern.
4. Review the projected jobs per day before saving.
5. Check the next run and later inspect a successful unattended result.