Neon
Cost
Performance
Background poll < 5 min interval hitting DB
Part of the Idle compute cost check · fix arrives as a guide
What it is
A background job polls the database on an interval shorter than five minutes.
Why it matters
Each poll wakes the compute and resets the autosuspend timer, so a job running every minute keeps the database running permanently. The polling itself is cheap; keeping compute alive is not.
How to fix it
Lengthen the interval past the autosuspend timeout so the endpoint can suspend between runs, or move the work to an event-driven trigger. Batching several frequent jobs into one less frequent run helps too.
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.