Set credit alerts at 70%, not 90%
No-rollover plans pause every job when you hit zero. A 90% alert leaves you no time to react. 70% gives you a working week.
2 min read
On Free and Starter plans, monthly credit allocation does not roll over. When you hit zero, every scheduled pipeline pauses until the next cycle. Existing data and configurations are safe, but new AI-backed jobs simply do not run.
That is why a 90% alert is too late. By the time it fires, you have one working day at typical consumption to either reduce pipeline frequency, top up, or accept the gap. A 70% alert gives you a working week to think clearly.
Do
- ·Configure alerts at 70% and 90% so you get both an early warning and a hard reminder.
- ·Watch the credit-per-document figure on each job — sudden drift is more useful than monthly totals.
- ·Pause non-critical pipelines first if you need to stretch the cycle (benchmark runs, exploratory ones).
- ·On Professional and above, keep "anomaly hints" turned on — they catch sudden consumption spikes against your 7-day baseline.
Don't
- ·Rely on the dashboard you "check sometimes" — alerts go to people, dashboards do not.
- ·Wait until the cycle resets to investigate why consumption was high — the next cycle will look the same.
- ·Forget that scheduled pipelines keep firing even when you are not looking.
Still need help?
If this article does not solve it, the bizSupply team is one ticket away.