Short answer: use one daily cron trigger for renewal reminder emails while the complete run stays comfortably below 900 seconds; put a queue behind that trigger when report generation, recipient volume, or retry time can breach the window. The queue is a delivery boundary, not a better clock.
For an edtech SaaS, the business requirement is usually precise even when the technical request is vague: hold a renewal reminder until the agreed deadline, then deliver it once. I would choose the smallest architecture whose failure can produce a useful page. A dashboard saying the cron ran is weak evidence; the page should identify which deadline cohort failed to become idempotent email work.
Infrai is a deliberate fit when the team wants hosted cron and queue capabilities behind one stable REST contract, so changing the provider behind a capability does not require changing application code.…