When the balance runs out
What stops when your balance reaches zero, what keeps working, the emails you get, and how to start again.
Evergreen doesn’t stop at the first sign of a low balance. It warns you early, it lets the work in flight finish, and it leaves your code alone. This page describes what happens at each point.
How your balance is described
The balance on Workspace settings › Billing carries a label.
| Label | What it means |
|---|---|
| In credit | You have more than about seven days at your recent pace, and over $20. |
| Running low | Less than about seven days at your recent pace, or under $20. |
| Not funded yet | You haven’t added funds. Add funds to start running sessions. |
| Used up | The balance is zero. Add funds to start new sessions. |
| On hold | Evergreen paused the account. You can’t start sessions until an Evergreen admin lifts the hold. |
Under the balance, the page shows what you’ve spent a day over the last week, so you can judge how long it lasts.
What happens as it runs down
- Running low. The balance reads Running low, and sessions keep running. When it reaches a level set by your recent daily spend, from $10 to $100, Evergreen sends the Low balance email once.
- Zero. New sessions, follow-up messages, and anything else that would start a turn are refused. A turn that’s already running finishes.
- A little below zero. The balance can run up to $5 below zero. Past that, Evergreen stops every live session in the workspace, including sessions still waiting to start, and sends the Balance exhausted email.
A stopped session keeps its branch and its pull requests. Nothing in your repositories is touched.
What waits
Automations keep arriving. An event refused for money waits and starts by itself, in the order it arrived, once funds are added. Events that wait more than 48 hours are let go. Scheduled automations that come up while the balance is empty are skipped. The Automations pages show Waiting for funds and the number of runs waiting.
Background work, which spends on its own, is skipped or falls back until there are funds.
What people see
Everyone in the workspace sees a banner when sessions are stopped, Your agents are paused. People who can add funds see Add funds in it, and everyone else sees who to ask. Only people who can add funds see a nudge that the balance is low, and they can hide it for a day.
A stopped session says that the Evergreen balance ran out and that your work is kept. Someone who can add funds gets Add funds there. Anyone else can ask the billing contact, or whoever looks after billing, to add funds from the same card.
Evergreen sends billing emails to the billing contact, the Owner, and anyone with the Billing delegation. Statements says when each one is sent. The ones about a low or empty balance are:
- Low balance.
- Balance exhausted, which says how many sessions were stopped.
- Funds restored, which lists the sessions that were stopped and how many automation events are waiting.
- Team waiting for funds, which names the person whose start was refused.
- Automations waiting for funds.
If your account is on hold, the banner says so and nothing starts until Evergreen lifts the hold. The same people get an email when Evergreen places the hold and another when it lifts it.
Start again
Add funds on Billing, which stays open however low the balance is. See Add funds. As soon as the balance is above zero, new sessions can start and waiting automation events begin on their own. Sessions that were stopped keep their branches and pull requests, so you can pick the work up again from there.
Tip
Turn on auto-reload so you rarely get here. A budget also stops spend earlier, without touching your balance.
Last updated