Scheduled jobs and cron triggers

A recorded cutoff and an operation key make the second delete delivery a no-op

A dev.to walkthrough of Node.js retention jobs puts recovery in the batch rather than the schedule, and the two sharp edges it exposes are the queue's visibility timeout and a key whose scope its own sample code changes.