Troubleshooting

Reminders Not Firing? Fix It in 5 Minutes

If your reminder never arrived, arrived late, or showed up in the wrong place, this checklist will isolate the cause fast.

A common support pattern is: “I asked for a reminder, then nothing happened.” Most cases are one of three issues: wrong timing syntax, timezone mismatch, or delivery/context mismatch.

Important: reminders are schedule-dependent. If the schedule is invalid, timezone is off, or destination context changed, the reminder may not appear where you expect.

Fast triage checklist

Confirm the reminder was actually scheduled (not just discussed).
Verify timezone assumptions (your local vs UTC).
Check where the reminder should deliver (same thread/session vs another context).
Check if the reminder time already passed when it was created.
Retry with a short known-good test: "Remind me in 2 minutes to say test".

Most common failure modes

Ambiguous time wording: “later tonight” without a precise time can misalign expectations.
Timezone drift: reminder interpreted in UTC while user expects local time.
Wrong destination: reminder fires in a different surface/session than expected.
One-shot confusion: recurring phrasing used when a one-time reminder was needed (or vice versa).
Past-time scheduling: date/time entered in the past, so job never behaves as expected.

Known-good reminder prompts

Use clear, explicit prompts when reliability matters:

Remind me in 20 minutes: "Stretch and drink water." Remind me today at 3:30 PM America/New_York: "Join product sync." Every weekday at 9:00 AM America/New_York, remind me: "Review #help backlog."

Avoid vague phrasing: “remind me this afternoon” is human-friendly but less deterministic than explicit date/time + timezone.

Delivery context gotcha (most missed)

Many "missing" reminders actually fired in a different context than the user was watching.

Dashboard vs Discord: these are separate conversation surfaces.
DM vs server channel: same agent identity, different destinations.
Thread-specific reminders: if created in one thread/session, they may not appear in another.
Cron/session-target mismatch: reminders bound to isolated runs can announce differently than expected.

Quick check: look in the exact place where you scheduled the reminder first, then check nearby surfaces (same server, DM, dashboard thread).

Timezone and DST edge cases

Include the timezone name (e.g., America/New_York) for exact-time reminders.
DST shifts can move expectations by an hour if timezone is omitted and UTC is assumed.
When testing, always include both “now” and expected fire time in your note so support can compare intent vs execution.

2-minute verification flow

Set a reminder for 2 minutes from now using explicit language.
Stay in the same conversation surface where you set it.
If it fires, your core pipeline works. The earlier failure was likely wording/timezone/context mismatch.
If it does not fire, capture details and escalate with the packet below.

Support-ready escalation packet

Reminder issue report Prompt used: Expected fire time + timezone: Where I expected delivery (DM/server/dashboard + channel/thread): Actual behavior: Current local time + timezone: Short 2-minute test result (pass/fail):

Best practice: for important reminders, include exact time + timezone + message body in one line.