Skip to content
Cook
Documentation Browse

When something goes wrong

Your workspace reached its spending limit

Cook stopped because the workspace reached its AI spend cap, used up its monthly credits, ran out of its agency's tokens, or is unpaid.

What happened

Cook stopped before starting more work. The message it showed says which of these four it was.

It reached its AI spend cap

Every workspace has an AI spend cap: a limit on how much Cook may spend on AI for it in a day or a month. The workspace reached it. A daily cap resets tomorrow (UTC); a monthly cap resets at the start of next month.

  • A workspace owner can raise the limit on the web in Settings → Plan, in the section called AI spend cap. Only an owner can change it.
  • If an agency runs your workspace and pays for it, the agency sets the limit. Ask them to raise it.

It used up this month’s credits

The plan’s credits for this month are used up. They reset at the start of the next month, on the date the message names.

  • To continue now, buy a credit pack from the card under the message, or in Settings → Plan.
  • If your workspace shares its credits with an agency’s other accounts, the agency buys more. Ask them.

Your agency’s tokens ran out

Your workspace is run by an agency, and the agency’s tokens are used up. Work is paused until the agency adds more. Ask them.

The workspace is read-only

The workspace’s subscription is unpaid, so it is read-only until it is paid. Everything is kept. Pay it in Settings → Plan, or, if an agency runs your workspace, ask the agency.

Then try again

Send the message again, run the routine again, or give the task to Cook again.