Falaah Falaah AI

Scheduled Messages

See everything queued to go out in your organization's name, check why a message is waiting, and stop a queued send before it reaches anyone.

Scheduled Messages is the register of everything Muin has queued to send in your organization’s name (thank-yous, reminders, post-event notes) and the one place to stop a message before it goes.

When you’d use this

  • You scheduled a reminder and then the event moved, so you need the old one stopped.
  • A parent asks why they got a message, and you want to see what else is lined up for them.
  • You want to confirm a thank-you really is queued before you tell a donor it is coming.
  • A send failed and you want to read the error rather than guess.

See what is queued

Go to Communications → Scheduled Messages. The screen is headed Scheduled Messages, with the line “Everything queued to go out in your organization’s name, and the one place to stop it.”

Column What it shows
Recipient Who the message is addressed to
Kind What kind of message it is, in plain language
Channel Email, SMS or the channel it will use
Sends When it is due to go out
Status Queued, Sent, Skipped, Failed or Stopped

Filter by status (All statuses, Queued, Sent, Skipped, Failed, Stopped) and by kind (All kinds, then each kind in use). The list shows 50 rows per page with Previous and Next controls.

Click a row to open the Queued message panel. It shows the recipient and their email, the kind and channel, when it sends, when it was sent, the status, how many retries have happened, the Last error if there was one, and the raw payload behind the message.

Stop a queued message

  1. Find the row. Only a message with status Queued can be stopped.
  2. Click Stop this message.
  3. Read the confirmation. It names the recipient and the kind of message, and says plainly that it cannot be undone.
  4. Choose Stop this message, or Keep it queued to back out.

The row moves to status Stopped. Stopping needs edit access to communications; with view-only access the action is not offered.

A message that has already Sent, Skipped or Failed cannot be stopped, it has already settled. Asking anyway returns an error naming the status.

The send clock

Muin checks the queue every five minutes and sends whatever is due. Two consequences worth knowing:

  • A message scheduled for 10:00 goes out between 10:00 and 10:05, not at 10:00 exactly.
  • You have until the next five-minute pass to stop something. Once the pass picks it up, the row reads Sent and stopping is no longer possible.

Each send is claimed once per tenant, and every queued message carries a unique key, so a message is never sent twice even if a pass overlaps the previous one.

Statuses

Status Meaning
Queued Waiting for its send time. This is the only status you can stop.
Sent Delivered to the channel. Check the Email Activity Log for what happened after that.
Skipped Muin decided not to send. Usually the recipient opted out, is suppressed after a bounce, or the notice was switched off between scheduling and sending.
Failed The send was attempted and rejected. Open the row and read Last error.
Stopped Someone on your team stopped it.

What it affects

  • Stopping a message affects that one send only. It does not switch off the notice that created it, do that under Settings → Communication & AI → Customer Emails.
  • Switching a notice off stops future messages of that kind being queued; anything already queued stays queued until you stop it here.
  • An opt-out or a bounce shows up as Skipped rather than Failed, because Muin chose not to send rather than failing to.

When it goes wrong

What you see What to do
“Unable to load scheduled messages” / “Something went wrong while loading the queue. Nothing was sent or stopped. Please try again.” A loading failure only. Nothing changed. Use Retry.
“Nothing is queued” Nothing is lined up. If you expected something, check that the notice is switched on in the Customer Emails console.
“No messages match these filters” Clear the status and kind filters.
Stop this message is missing on a queued row You have view access but not edit access to communications. Ask your owner or admin.
A row shows Skipped and the recipient says they never got it That is the expected result of an opt-out or a bounce suppression. Open the person’s record to see their contact status and whether their address is bouncing.
A row shows Failed with retries Open the row and read Last error. A bad address is fixed on the person’s record; a provider error usually clears on the next retry.

Next step