Sync Schedules
Every connection in Propexo Connect needs a schedule that determines when syncs run. Two options are available:
| Schedule Type | How It Works |
|---|---|
| Cron | Syncs run on a recurring cadence defined by a cron expression |
| Manual | Syncs only run when you explicitly trigger them |
Cron Scheduling
Cron expressions give you precise control over sync timing. Run syncs at specific times, on particular days, or at any recurring interval your workflow requires.
Propexo Connect uses the standard Unix cron format — five fields: minute, hour, day-of-month, month, and day-of-week. All schedules run in UTC.
Common Patterns for Operational Data
| Pattern | Cron Expression | Why It's Useful |
|---|---|---|
| Every hour | 0 * * * * | Keep inspection, messaging, or ticketing data relatively fresh for operational dashboards |
| Daily at 3 AM UTC | 0 3 * * * | Nightly sync for reporting — captures a full day of vendor-side activity before your morning analytics jobs |
| Twice daily | 0 6,18 * * * | Balance freshness and load for mid-size portfolios |
| Weekdays at 6 AM UTC | 0 6 * * 1-5 | Skip weekends for data that primarily changes during business hours |
| Every 6 hours | 0 */6 * * * | Good default for datasets that change steadily through the day across time zones |
How Cron Scheduling Works
Once a cron-scheduled connection is created, syncs begin firing at the next time that matches the expression. If a sync is still running when the next scheduled time arrives, the new sync starts as soon as the in-progress sync completes — no scheduled execution is skipped.
Manual Syncs
When a connection uses manual scheduling, no syncs run automatically. Click the Manual sync button in the console to trigger a sync whenever you're ready.
Manual mode is useful for:
- Initial testing of a new connection
- Data sets that change infrequently (e.g., a portfolio or locations list that only updates on rare corporate events)
Operational Details
- One sync at a time — Each connection runs a single sync concurrently. If a new sync is due while a previous one is still running, it queues and begins once the active sync finishes.
- UTC only — There is no time zone selector. Convert your desired local time to UTC when writing cron expressions.