Use a persistent worker below the scheduler minimum

When required cadence is shorter than the hosting scheduler’s supported minimum, replace the invalid schedule with one persistent worker rather than pretending the schedule is active. Run iterations sequentially, bound each request below the interval, use one replica, and add server-side exclusion because a client abort does not prove remote work stopped. Configure restart policy and graceful shutdown so a process replacement does not create another owner. This pattern is appropriate for modest fixed-rate work; use a durable queue when backlog, per-job retries, or horizontal throughput are required.

Applies when: a periodic task must run faster than managed cron supports. Keywords: cron minimum interval persistent worker sequential overlap timeout restart