Schedules

What’s seeded for you

Proxploy seeds two system schedules the first time it starts: a nightly catalog refresh, and an hourly metrics maintenance pass. Both are ordinary cron schedules, visible and disableable like anything else; if you turn a system schedule off, it stays off across restarts rather than quietly re-enabling itself.

Creating your own

Any schedulable job (a backup run, for instance) can be put on a cron schedule of your own. Proxploy checks a schedule’s cron expression against the same validation the scheduler itself uses to decide when to fire, so a schedule that would never fire correctly is rejected at creation time rather than silently sitting inert.

Running now

Every schedule has a “run now” action that fires it immediately, bypassing its cron timing without changing it, useful for testing a new schedule or catching up on a backup without waiting for its next scheduled time.

The scheduler checks for due schedules roughly every 30 seconds, so expect up to that much latency between a cron time landing and the job actually starting.