All guides
Routines & automation

Routine not arriving

Free

Find out why a brief or digest did not arrive in a chat, by email or as a push, and how to get it going again.

  1. 1

    Open the routine

    Check Last delivery for each destination.

  2. 2

    Read the status

    Delivered, Couldn't send, Disconnected or Skipped.

  3. 3

    Fix and resume

    Reconnect the chat, change a setting or adjust the plan.

Start with the routine itself. In Settings → Automations, open the routine and look at Last delivery. It shows what happened for each destination on the latest run, and when.

What each status means

  • Delivered: Otto handed the message to that destination.
  • Sending: the run is still delivering.
  • Couldn't send: the destination refused or failed. Hover the row for the reason, then use Run now to try again.
  • Disconnected: the chat app is no longer linked, or its access was revoked. Otto skipped it, and your other destinations still got the run.
  • Skipped: Otto did not send to that destination on this run.

A chat is disconnected

Select Reconnect next to the destination, or open Settings → Integrations, pick the connection and use Reconnect this connection. Otto also posts one notice in the app when a chat becomes unreachable, so you are not left guessing. Once the chat is reconnected, delivery resumes by itself and the routine does not need editing. Digests missed in between are not sent afterwards, but Otto offers to send the latest one now. See Private chat integrations.

Your plan

Chat apps need Plus or above, and Telegram, Slack and Discord are the ones you can connect today. Free delivers to Otto, email and push. Plus connects 1 chat app with up to 2 chat destinations per routine, and Pro connects 6 chat apps with up to 4 per routine. If you move to a smaller plan, chats over the new limit pause with their history kept. Event triggers need Plus or above, and the shortest schedule is daily on Free, hourly on Plus and every 15 minutes on Pro.

Quiet hours and mute

A chat you muted with "mute 2h" holds its updates until the mute ends. Each routine also holds its chat messages overnight, 22:00 to 07:00 in its time zone by default, and sends them when the window ends. Open the routine's card and check Quiet hours for chat to change or remove it. Otto's feed, email and push are not held. Quiet hours in Settings → Alerts pause alerts during your window and do not delete anything. For push, also check that the category is on in Alerts and that notifications are allowed for the browser or app in your device settings. See Notifications, alerts and daily briefs.

An empty run

A scheduled run with nothing to report sends a short "Nothing new since" note at low priority. It can look like a missing brief when push is quiet. The routine's history shows it as an empty run.

Email did not show up

Look in your spam folder and mark the message as not spam. Last delivery shows Delivered once Otto has handed the email off.

Common questions

Will I get the briefs I missed while a chat was disconnected? No. Otto does not backfill them, but it offers to send the latest one now.

The brief arrives in the app but not in Slack. Why? Check Last delivery for that destination. If it says Disconnected, reconnect. If the routine has no Slack destination, add one from the routine or by asking Otto.

Is a disconnected chat an error on my routine? No. The routine keeps running for its other destinations.

If a routine is not running at all, see the routines guide for plans and limits, or ask Otto "why didn't my morning brief arrive?".

How to use it

  1. 1Open the routine. In Settings → Automations, open it and read Last delivery.
  2. 2Fix the destination. Reconnect a disconnected chat, or check quiet hours, mute and your plan.
  3. 3Send the latest. Use Run now to deliver a fresh result once it is fixed.

Just ask Otto

“Why didn't my morning brief arrive?”
Configure in Settings