Drıftstack docs
Docs

Recipe limit reached / session already saved as a recipe

You might be here because: “Your plan keeps up to N recipes, and this account has N” · “Delete a recipe to save a new one” · “This session is already saved as recipe” · “Delete that recipe to save the session again” · “429 tier-limit when saving a recipe” · “409 conflict saving a recipe” · “can’t save another recipe” · “how many recipes can I keep” · “save the same session twice” · “A usage limit was reached. Wait a moment or review your plan, then try again”

Short answer

A recipe is a saved copy of the steps a finished AI session took, not of its transcript, and two rules stop a save: each plan keeps a fixed number of recipes, and a session is saved once. Delete a recipe you no longer need, then save again; to save the same session under a new label, first delete the recipe it already made.

Check first

  • Which sentence did you get? “Your plan keeps up to N recipes, and this account has N. Delete a recipe to save a new one.” is the limit (HTTP 429 tier-limit); “This session is already saved as recipe … Delete that recipe to save the session again.” is the one-save rule (HTTP 409 conflict).
  • Working in a team owner’s workspace? A recipe saved there belongs to the owner and counts against the owner’s plan, and every recipe action there needs the admin role.

Likely causes and fixes

  1. You are at the plan’s number. Recipes per plan: Trial 10, Starter 50, Pro 200, Team 500, Scale 1,000; Enterprise is set by contract. Older plans that are no longer sold keep their own numbers. The refusal carries limit and current. Fix: delete a recipe, or move to a higher plan — self-serve for Starter, Pro and Team from the dashboard → Billing → Choose a plan; Scale and Enterprise are arranged with a person.

  2. This session is already a recipe. A session is saved once; the 409 names the existing one in recipe_id. An exact repeat of the same save (same session, label and description) returns that recipe again and stores nothing new. Fix: delete that recipe if you want the session saved under a different label.

  3. The desktop app shows a generic sentence — “A usage limit was reached. Wait a moment or review your plan, then try again.” for the 429, “The item changed or is busy. Refresh and try again.” for the 409; the exact reason is in the API response.

  4. “AgentSession … not found” (404). The session must belong to the workspace you save into.

If it still fails

If you deleted a recipe and the save is still refused, press Talk to a person in this chat (or open Help) and include your plan, the limit and current values from the response, the session id and, for a 409, the recipe_id.