Troubleshooting
Channel status, test sends, the delivery log, Discord permissions, and what happens to notifications when a plan lapses.
Channel status
Each channel shows its status next to its name:
| Status | Meaning |
|---|---|
| Active | Working. |
| Waiting for a test | A new Discord channel whose first test post didn't arrive. Nothing is posted until a test gets through. |
| Failing | The last 3 notifications couldn't be delivered. Nabbed keeps trying. |
| Disabled | Nabbed stopped sending. The banner above the channel says why. |
| Off | Someone switched the channel off. |
| Paused | A Discord channel while the household is on Free. See When a plan lapses. |
How a channel gets disabled
When a notification can't be delivered, Nabbed tries again after 30 seconds, 2 minutes, 10 minutes and 30 minutes. Only if the last try fails does it count against the channel.
- 3 failures in a row and the channel is Failing, with a banner.
- 5 failures in a row, the first at least 24 hours ago, and it's Disabled. It takes both, so one bad hour can't turn a channel off.
- A permanent error disables it at once: the email provider rejects your address, or the Discord bot lost access to the channel, was removed from the server, or the channel was deleted.
Being rate-limited by Discord or the email provider doesn't count. Any notification that's delivered resets the count.
When a channel is disabled, Nabbed tells you in the notification centre, with a title such as "Email notifications are off". For a household channel, the owner and admins are told.
Turn a channel back on
Fix the problem, then choose Send test on the channel. A test that arrives turns it back on.
Send a test
Send test on a channel sends "Test notification from Nabbed" straight away. It's the quickest way to check a channel, and the way to turn a disabled one back on.
- You can send up to 5 tests a minute to a channel. After that, Nabbed asks you to try again in a minute.
- A test that fails because of a temporary problem, such as Discord not answering, doesn't count against the channel. A permanent error disables it, with the reason.
- Tests appear in the delivery log as Test.
- Only owners and admins can test household channels.
Read the delivery log
Settings → Notifications → Delivery log lists every notification Nabbed sent to your channels and the household's channels, or decided not to send, and why. Filter it to Delivered, Queued, Skipped or Failed. The log keeps 7 days on Free and 30 days on Pro.
Each entry shows when it happened, the notification's title, the event, the channel, and how many attempts it took if there was more than one.
| Status | Meaning |
|---|---|
| Queued | Waiting to be sent. A delayed one says when it's due: a Ready to watch email "unless you see it in Nabbed first", or a Discord post "with any more episodes that arrive by then". If a try already failed, the error shows. |
| Sending | Being sent now. |
| Delivered | The email provider or Discord accepted it. If you can't find an email, check your spam folder. |
| Failed | Every try failed. The error shows. |
| Skipped | Nabbed decided not to send it. The reason shows. |
Why a notification was skipped
| Reason shown | What it means |
|---|---|
| Not essential, so not emailed on the Free plan | On Free, only essential alerts are emailed. |
| Over the essential email limit (1 per problem every 6 hours, 10 a day) | One of the Free plan's limits on essential alerts. |
| You saw it in Nabbed first | A Ready to watch email for a notification you read in the app within 10 minutes. |
| Email was off or disabled when it was due | Email was switched off, or disabled, after the notification was queued. |
| The channel was off or disabled when it was due | The same, for a household channel. |
| You'd left the household | You left before it was sent. |
| Household channels need Pro, and the plan had changed | The household left Pro after the post was queued. |
Not in the log at all?
The log only lists notifications that were meant for a channel. Nothing appears when:
- the event isn't sent to you (see who gets each event)
- the event is switched off for that channel
- it's below the channel's minimum severity
- the channel was off or disabled at the time
- it's for a household channel and the household is on Free
Check the notification is in your notification centre, then check the channel's settings.
Emails don't arrive
- Check Email notifications is on and the channel is Active.
- Check the event is switched on under What you hear about, and isn't below your Minimum severity.
- On Free, only the owner and admins get emails, and only for essential alerts.
- Choose Send test, then look in your spam folder as well as your inbox.
- Look the notification up in the delivery log.
Discord permission problems
When you add a channel, channels the bot can't post in are locked and say which permission is missing. In Discord, open the channel's settings → Permissions, add the Nabbed role and allow View Channel, Send Messages and Embed Links. Then choose Refresh in Nabbed.
If the bot loses access later, Nabbed disables the channel and the banner says why:
| The banner says | What to do |
|---|---|
| The Nabbed bot can't post in the channel any more (Missing Access, or Missing Permissions) | Give the Nabbed role View Channel, Send Messages and Embed Links in that channel, then choose Send test. |
| The channel was deleted, or the Nabbed bot was removed from the server | If the bot was removed, add it to the server again with Add Discord channel, then choose Send test on the channel's card. If the channel was deleted, remove it and add another. |
When a plan lapses
If your household leaves Pro:
- Discord channels show Paused, and nothing is posted to them.
- Email goes back to essential alerts for the owner and admins.
- Your settings stay as they were: channels, event choices and minimum severities.
- Discord posts that were already queued are skipped, with "Household channels need Pro, and the plan had changed".
- The delivery log keeps 7 days instead of 30.
- The @Pro and @Lifetime Discord roles follow the plan.
When the household is back on Pro, delivery starts again with the next notification. Nothing that happened in between is sent later, so there's no backlog.