Source code
Cost
Performance
Cron runs every minute on full scan
Part of the Cost controls check · fix arrives as a guide
What it is
A scheduled job runs at high frequency — every minute or so — and does a full scan or full re-computation on each run rather than processing only what changed.
Why it matters
The work is mostly wasted: the same rows are read 1,440 times a day to find the handful that moved. Cost and database load scale with the schedule and the table size together.
How to fix it
Process incrementally using an updated-at watermark or a queue of changed ids, and lengthen the interval to match how fresh the result genuinely needs to be.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.