Skip to content
Troubleshooting Member Admin

My reminders aren't firing

My reminders aren’t firing

You set a reminder through Dailybot or expected an automated nudge, but nothing arrives in chat. Reminders depend on correct timezone, enabled features, working platform permissions, and sometimes plan limits. They also share infrastructure with other function-calling paths, so Discord or Slack permission issues can look like “reminders are broken” when the scheduler actually ran.

Quick check

  • Timezone — Confirm your personal timezone in Dailybot and the org default; reminders fire on those clocks.
  • Reminder status — Open the reminder or automation list in the web app and verify the item is active, not paused or expired.
  • Plan — Ensure recurring or advanced reminders are included on your current plan.
  • Channel access — The bot must be able to message the channel or user where the reminder should land.
  • Quiet hours — Org-level quiet hours can delay or batch reminders until an allowed window.

Common causes and fixes

Timezone mismatch

A reminder set for “9:00” follows the timezone on the account that created it unless the UI states otherwise. Travel, daylight saving changes, or a wrong org default produce “missing” reminders that actually fired at another hour. Align personal and org timezones, then edit and save the reminder so the next run picks up the new offset.

Reminder disabled or superseded

Paused automations, archived check-ins, or duplicate reminders with the same label can confuse people. Audit active reminders in the dashboard. Delete stale test reminders that might have consumed quota or blocked a slot. If a reminder ties to a check-in, confirm the check-in itself is still scheduled.

Feature not available on plan

Some reminder types or high frequency schedules require a paid tier. If billing lapsed, Dailybot may stop scheduling new runs while showing historical entries. Upgrade or trim reminders to what the plan allows, then toggle them off and on to reschedule.

Platform or function-calling failure

When slash commands or bot posts fail broadly, scheduled sends can fail too. On Discord, verify role hierarchy and slash registration (see Slash commands aren’t working in Discord). On Slack, re-check app installs and channel membership. For any platform, confirm the bot is not removed from the target channel.

User notifications muted

Individuals who mute the bot or the channel will not see reminders even though logs show delivery. Ask the user to unmute or check notification rules in Slack or Discord.

If none of this worked

Before contacting support, gather:

  • Reminder text or internal name and when it should fire
  • Your timezone setting and org timezone
  • Platform where you expect the message
  • Whether other Dailybot messages work in the same channel
  • Approximate date the issue started
  • Steps you already tried from this article

Then contact Dailybot support from the Help or Contact options in the product or on the website.