Short maxDuration with active crons

What it is

The project has active cron jobs while maxDuration is set low enough that they may be cut off.

Why it matters

A cron killed mid-run leaves whatever it was doing half-finished — a partial batch, an interrupted sync — and because it is scheduled, nobody is watching when it happens.

How to fix it

Raise maxDuration for the cron routes specifically, or make the job resumable so it processes a bounded batch per run and picks up where it stopped.