---
title: Why you are not being notified
url: https://tideswell.xyz/docs/troubleshooting/not-being-notified
description: Check the Inbox first. Whether the alert is there tells you which half of the system to look at.
---

> Documentation index: fetch https://tideswell.xyz/llms.txt to discover every page before exploring further.

# Why you are not being notified



There is one check that splits this problem in half, and doing it first saves most of the work.

**Look in your Inbox.**

If the alert **is** in your Inbox, the alert worked and something on your device or in your
personal settings stopped the buzz. If it is **not** in your Inbox, the alert never reached you
at all and the cause is upstream.

## The alert is in your Inbox but nothing buzzed [#the-alert-is-in-your-inbox-but-nothing-buzzed]

Work down these.

**Are notifications switched on for this device?** They are per browser and per device, so your
laptop being on says nothing about your phone. Turn them on and send a test, per
<Ref to="notifications/turn-them-on" />.

**On an iPhone, is Tideswell on the home screen?** Safari only allows notifications after that,
and it is the usual reason a phone stays silent.

**Did it arrive inside your quiet hours?** They default to 22:00 to 07:00 and they **drop**
notifications rather than holding them, so a one-off ping sent at 3am is gone. The Inbox item is
the record. See <Ref to="notifications/quiet-hours-and-levels" />.

**Is the category switched off for you?** Task reminders, low-stock alerts and notable orders
each have a personal switch.

**Is the channel muted?** A channel level overrides your default, so one muted channel is silent
while everything else works. See <Ref to="notifications/mute-or-follow-a-channel" />.

**Did you block notifications in the browser once?** The page tells you to allow them in the
browser's own settings and reload, because that block cannot be undone from inside Tideswell.

## Nothing is in your Inbox either [#nothing-is-in-your-inbox-either]

Then the alert never fired or never included you.

**Is the automation switched on**, and is its module on? See
<Ref to="automations/turn-one-on-or-off" />.

**What does the health line say?** "No alert" means it ran and there was nothing to report, which
is usually the real answer. A failure or a skipped run names its reason. See
<Ref to="automations/check-it-worked" />.

**Are you on the recipient list?** And separately, **do you still have the store access** that
makes you eligible? Losing that access silently stops the alert even with your name still ticked
on the list.

**Is the amber banner up** on the automations screen? Then automations are off for the whole
environment and nothing runs at all.

## A workflow was meant to notify somebody [#a-workflow-was-meant-to-notify-somebody]

A workflow's **Notify** step sends a push only, and a push landing inside somebody's quiet hours
is dropped rather than held.

Read the run. "Told 3 people, 2 devices buzzed" is a normal outcome rather than a fault, and
"no push went out" tells you it was quiet hours or notifications being off.

A Notify step aimed at a department with nobody active in it fails, and the run says so. See
<Ref to="workflows/notify-someone" />.

## Task reminders specifically [#task-reminders-specifically]

Reminders only go to the **assignee**, on tasks that are unfinished and **have a due date**.

A task you created and handed over reminds them rather than you. A task with no due date never
reminds anybody. See <Ref to="notifications/task-stock-and-order-alerts" />.

## Nothing works for anybody in the workspace [#nothing-works-for-anybody-in-the-workspace]

Then it is one of the two workspace-wide causes: automations switched off for the environment,
or the module that owns those alerts switched off.

Both are visible from the automations screen, and the second is in
<Ref to="workspace-admin/modules" />.