Why am I not receiving Slack, ClickUp or email notifications?

If launches finish, rules fire, or the daily digest runs but nothing lands in Slack, ClickUp, or your inbox, the cause is almost always one of five small gaps. The fastest way to isolate it is the Send test notification button in Configuration → Notifications, which fires every connected channel at once and shows a per-channel status pill so you can see exactly which one broke.

First: run the channel test

The test fires email always, plus Slack and ClickUp whenever they're connected — independent of your per-event toggles, so it confirms the plumbing even if no event is routed yet. Not configured means the channel isn't connected; a red error means the dispatch was attempted but failed (and usually names the reason).

Slack: private channels need /invite @uplads

uplads installs as a Slack bot. Slack's own rule is that the bot can post to public channels automatically, but it can only see and post to a private channel once it has been added as a member.

If you picked (or want to pick) a private channel and messages never arrive — or the channel doesn't appear in the picker at all:

1. Open the channel in Slack.
2. Type /invite @uplads and send it.
3. Back in Configuration → Connections → Slack, open the channel picker and click Refresh to re-fetch the channel list.

Private channels show with a lock icon; public ones appear without inviting the bot first.

Legacy webhook users: the "Reconnect needed" banner

Slack used to connect with an incoming webhook locked to one channel. We replaced that with a bot install so you can pick any channel from a dropdown. If you connected the old way, the Slack card shows an amber Reconnect needed banner — and while it's showing, the new channel picker can't load and notifications may not route correctly. Click Reconnect Slack (a ~30-second OAuth re-install), then pick your default channel. See How to connect Slack and choose a notification channel.

ClickUp: task mode vs. chat mode

ClickUp routing is per event, with three modes:

• Task — posts a comment on the single task you saved. Requires a saved target task.
• Chat — posts a message into the saved ClickUp Chat channel. Requires a saved chat channel.
• Off — skips ClickUp for that event.

So if a launch-finished alert is set to Task but you only picked a chat channel (not a task), nothing posts. Make sure the destination matching the mode is saved in the ClickUp card. See How to connect ClickUp for task and chat notifications.

Per-event routing is turned off

This is the most common cause. Connecting a channel does not start sending everything — routing is a grid of (event × channel) toggles in the Notifications tab, where each row is an event (rule matches, launch finishes, daily digest, budget burn, weekly audit, and so on) and each column is a channel. For email and Slack the cell is an on/off toggle; for ClickUp it's a mode picker (Off / Task / Chat).

Watch for:

• New email categories default to off, so you opt in per event.
• If you ever used Turn all notifications off, every event toggle was wiped (connections stayed alive) — re-enable the events you want.
• The daily digest, budget-burn alerts, and weekly audit each have their own enable switch and schedule. See How to set up notifications, daily digest and weekly audit.

Email going to the wrong address

uplads sends notification emails to the notification email in the Notifications tab. If that field is blank, it falls back to your login account email. So if emails arrive at an unexpected inbox (or not at all):

1. Open Configuration → Notifications and check the notification email field — a per-account override there always wins over your auth email.
2. If it's blank and your auth email is an alias or shared address, set an explicit address.
3. Save, then run Send test notification to confirm the email lands.

Still nothing?

• Re-run the channel test and read the per-channel pill — a red error names the failing channel and reason.
• Confirm the connection is healthy in Configuration → Connections (Slack shows "Connected"; ClickUp shows a saved token).
• If controls look greyed out, your role may be view-only — see Why is configuration greyed out or read-only for me?.