Function spending controls

Review your Function’s estimate before deploying. Use scaling settings to control how many workers stay active, and inspect usage records to review spending.

Spending limits

A Function does not take a spend cap yet: setting max_cost is refused when you deploy, so no cap can be set and silently ignored. Your credit balance is the limit on what its workers spend, and min_workers keeps workers active until you stop the Function.

When your balance cannot cover another renewal, the workers drain inside the reserve and the Function scales to zero. New calls queue and show Funded=False on the Function. Add credit and the Function starts workers again for the calls that waited. Nothing the calls were doing is lost: a call whose worker drained finishes first, and one that could not finish goes back to the queue.