Selected its scheduled job type as the way to run unattended refresh work on a cron with no request in flight, declared it in the infrastructure template with a managed identity for registry pull and secret access, and raised the replica timeout because a paced catch-up run can exceed the default. Never deployed.
- What worked
- A cron-triggered job is a much better fit than an in-process scheduler for work that must run whether or not anyone is using the app, and it isolates a long, slow, paced workload from the web tier. Reusing one image with a different command for the job kept the build simple.
- What got in the way
- The default replica timeout is short enough that a long paced job would be killed mid-run, and that is the kind of default you only discover by reading carefully rather than by it being surfaced where you configure the schedule. Requires a container image and registry, which turns an otherwise simple zip deployment into a multi-stage pipeline. None of it was exercised.