Plan limits and backup engines
What happens when a bot's engine hits its plan limit, how to name a backup engine that answers in the meantime, and how to make a routine wait for the limit to reset.
What you see at a limit
When a bot's engine reports that its limit is reached, Murage does not quietly send your message somewhere else. The chat shows a card. If the bot has no backup, the card lets you pick an engine for this message or choose Wait for the limit to reset. Tick Also use it next time and Murage keeps that choice.
A plan you signed in with in SettingsModels says it in the row: Plan limit reached. Bots using this plan pick up again after 14:30. Nothing was moved to another provider.
Name a backup engine for a bot
Step 1
Open the bot's model settings
Open Bot settingsModel.
You're done when: you can see the engine and model the bot uses now.
Step 2
Choose the backup
Find When this engine is at its limit. It reads Another engine answers your message when this bot's engine is at its limit. Without one, a card lets you pick or wait. Choose an engine from the list. Only engines you have set up and turned on appear, and the bot's current engine is left out.
You're done when: the row names the backup engine.
Step 3
Decide about routines
Tick Also for routines if a routine on this bot should switch to the backup too. The hint reads Routines carry on only on a plan or key you already pay for. Leave it unticked and a routine that hits the limit waits instead.
You're done when: the tick box matches what you want routines to do.
The backup is per bot, so one bot can fall back to Fuigo on a Flux Router model while another waits. Our advice: let the Chief of Staff fall back and make the bot that writes code wait, because an hour's delay costs less than code written on a weaker model.
Make a routine wait for the reset
In the routine editor, open Repeat and choose When a limit resets. Pick the Engine to watch. The routine starts when that engine's limit resets, instead of at a time you guessed.
Good to know
- Desktop app only. The backup row and the limit-reset repeat are set in the desktop app.
- Your own plans and keys. A backup runs on a plan or key you already have. Murage never moves work to another provider on its own.
- Per bot. Each bot has its own backup. A bot without one shows the card and waits.
- Plan sign-ins pause. A ChatGPT or Grok plan sign-in pauses at its limit and shows the time it picks up again.