Why a call was stopped

Every AI call is checked before it runs. When one is stopped, nothing is spent. Here is what each reason means and what to do.

A budget you set was reached

The call would have taken one of your budgets past its limit, so it was stopped before anything was spent.

Wait for the day or month to start again, or raise the budget. Raising one asks you to confirm. Go there

Your spending is paused

You, or an admin of your workspace, paused all AI spending. Every call is stopped until it is resumed.

Resume spending on Overview when you're ready. Go there

This key's monthly limit was reached

The programmable.run key the call used has a monthly dollar limit, and this month has reached it.

Raise the key's limit on Keys and agents, or wait for next month. Go there

Not enough credits

The call was going to be paid with your Programmable credits, and there weren't enough for it.

Add credits on your Programmable account, or add your own provider key so calls use it instead.

This needs your own provider key

This kind of call can only run on your own key for the provider, and there isn't one saved.

Save your provider key on programmable.dev. Spend never stores or shows keys.

A rule stopped it

One of your safety rules matches this call and says to stop it.

Change or remove the rule on Routing rules. Go there

We couldn't check it, so we stopped it

Before every call the platform checks your budgets and rules. That check couldn't be made just now, and a call that can't be checked is never let through.

Try again in a minute. Nothing was spent.

Too many calls at once

Calls came in faster than the limit for your key.

Slow down and try again after the wait the answer names (Retry-After).

A sign-in token isn't a key

The model endpoint takes API keys only. The call sent a sign-in token from a browser session.

Use an API key from programmable.run.

The key wasn't accepted

The key is wrong, has expired or was revoked.

Make a new key on programmable.run.