Routines not running

Routines run on your computer. The most common reason a routine didn't run is simply that the computer was asleep or Murage wasn't running at the scheduled time.

Check the basics#

• Was Murage running? A routine only runs while your computer is on and Murage is running. Closing the window is fine if Murage keeps running in the menu bar or system tray; quitting it isn't.
• Was the computer asleep? A sleeping computer doesn't run anything. Adjust your power settings if routines need to run overnight.
• Is the routine on? Imported routines arrive paused. Check the Paused routines list on the Routines page.
• Is the bot working? Test the bot in a normal chat. If its engine can't answer, the routine can't either.

Late and missed runs#

If Murage was off when a routine was due, it catches up when Murage starts again, as long as the run is no more than 12 hours late. Later than that, the run is marked Missed and the routine waits for its next time.

Routine problems#

The Routines page has a Routine problems list: failed and missed runs you haven't opened yet. Open a run to see its record and what went wrong. Mark all as read clears the list once you've dealt with them. A routine that keeps failing shows its streak there.

A run was skipped because the last one was still going#

A scheduled time is skipped while an earlier run of the same routine is still going. Run now is separate and always starts a run. If this happens often, the routine is trying to do too much for its schedule. Make the job smaller, space the runs out, or raise its duration.

It ran but asked for approval and stalled#

A routine runs at its own approval level, set in the routine editor under Advanced → Approvals for this routine. One you haven't set follows the bot's level when each run starts. When a run hits a question or an approval, Murage tells you at once and the run ends as Waiting on you. Open it with Review, answer, and it carries on from there. If the same card comes up on every run, choose Always allow for this routine on it. Reading your keys always asks.

It ran but I didn't get the result#

A routine reports in Murage, in its own conversation. It doesn't send its report to Telegram, Slack or Discord by itself. Look in the Inbox, the bot's conversation, or the menu bar count. If you want a message elsewhere, ask the bot to send one as part of the job, and it'll go through approvals.

A watch doesn't notice changes

Watches check files in a bot's working folder, up to 1 MB, not web pages. To keep an eye on a website, use a daily routine that checks the web and tells you what changed. A watch also stops once it reaches its end date or its maximum number of checks.

Times look wrong

Bots are given the date, the time and your time zone on every turn. If the times look off, check your computer's clock and time zone. The default House Rules tell bots to write every time with its time zone.

A routine a bot suggested never appeared

A bot can propose a routine, but it's only created when you press Confirm on its card. Check the Inbox for an unanswered proposal.

Webhooks don't start anything

• The webhook receiver listens only on your computer, at 127.0.0.1:8800. A cloud service can't reach it without your own tunnel.
• Check the sending app uses the address and secret Murage gave you, or the bearer token in a header.
• Check the webhook's recent attempts in Routines → Webhooks.

See also: Routines and webhooks.