Why you are not being notified

Tideswell notifications reach you in two places: a row in Work › Inbox and a buzz on each device you switched on. One check splits this problem in half, so do it first. For the background, see What are notifications?.

Where do you start?

Look in Work › Inbox. If the alert is there, it worked, and something on your device or in your own settings stopped the buzz. If it is not there, the alert never reached you, and the cause is further upstream.

Two kinds of buzz never leave an Inbox row: task reminders and a workflow's Notify step. They have sections of their own further down.

Why is the alert in your Inbox but nothing buzzed?

Something on your device or in User menu › Account settings held it back. Work down these checks in order.

Are notifications switched on for this device? Each browser and each device is its own switch, so your laptop being on says nothing about your phone. Turn them on and send a test, as in How to turn on notifications.

On an iPhone or iPad browser, is Tideswell on your home screen? Safari only offers notifications once it is. In the iPhone app, you allow them when the app asks, straight after you sign in.

Did it arrive inside your quiet hours? They are on by default, from 10pm to 7am, under User menu › Account settings › What buzzes you. A buzz due inside them is not sent later, so the Inbox row is your record of it. See How to set quiet hours and your default chat level.

Is your time zone right? Quiet hours start and end by Your time zone, in the same section. It either follows your device or stays on a zone you picked, and a wrong zone moves the quiet window. See How to set your time zone.

Is that kind of alert switched off for you? What buzzes you has a switch for each of these:

• Task reminders.
• Low-stock alerts.
• Notable order alerts, which also covers late purchase orders and overdue supplier bills.
• Suggestions, for a suggested change waiting on you. The suggestion still waits in your Inbox.

Is the channel muted? A channel's own level overrides Default for channels, so one channel set to Nothing stays silent while everything else works. See How to 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. Change it there, because the browser remembers the block.

Why is nothing in your Inbox either?

The alert never fired, or never included you. Most of these checks need an admin, because they live on Brain › Automations.

Is the alert switched on? Each alert in the Alerts list has its own switch. See How to turn an automation on, off, or run it now.

What does its Latest column say? Nothing new to send means it found the same things as before and everyone was already told, or that Wait between alerts is holding new ones back. Each product, order or bill alerts once and stays quiet until it recovers.

A failure or a skipped run gives its reason. See How to check whether an automation worked.

Are you among the people who hear it? The Who hears about it column says. An alert set to go only to people somebody picked reaches nobody else.

Do you still hold See sales, inventory, reports and the daily brief? These alerts only go to people who do. Losing that permission stops them, even with your name still picked. See How to choose who gets an alert and how often.

Is the module that owns the alert switched on? Low-stock alerts belong to the Inventory switch in Settings › Modules, not Store. Switching Inventory off warns that it stops The low-stock watchdog, and its push alerts. See How to switch parts of Tideswell on and off.

What if a workflow was meant to notify somebody?

A workflow's Notify step sends a buzz only. It leaves no Inbox row, and a buzz that lands inside somebody's quiet hours is not sent later.

Open the workflow's Runs tab and read that step. It starts Told 3 people, then says either how many devices buzzed or no push went out (quiet hours, or notifications are off). Both are normal outcomes rather than faults.

A Notify step aimed at a department with nobody active in it, or at a member who has left the workspace, fails, and the run says so. See How to notify someone from a workflow.

Why did a task reminder not arrive?

Reminders go only to the task's assignee, on tasks that are unfinished and have a due date. They start a week before the due date and come closer together as it nears.

A task you created and handed over reminds them rather than you. A task with no due date never reminds anybody. A snoozed reminder stays quiet until the snooze ends.

A reminder that falls inside your quiet hours goes out on the first run after they end. Task reminders buzz but leave no Inbox row, so the Inbox check does not apply.

In a workspace where the Agent checks in on late tasks, a task up to two weeks overdue gets no Overdue: buzz. The Agent asks about it in its Inbox or a Chat direct message on the first working morning after the due date, per How to have the Agent check in on late tasks.

Check your Task reminders switch, then ask an admin whether Task due reminders is switched on in the Alerts list. See How to control task, stock and order alerts.

Why does nothing work for anybody in the workspace?

Then the cause is a module, because a switched-off module stops its alerts for everyone. In Settings › Modules:

• Automations off stops every alert, including task reminders.
• Store off stops the alerts about orders and store data.
• Purchase orders off stops the late purchase order and overdue bill alerts.
• Inventory off stops low-stock alerts and stock count sign-off notifications.

While Automations is on, an admin can open any alert on Brain › Automations and see the module it is waiting for. See How to switch parts of Tideswell on and off.