Troubleshooting
Daily Econ Calendar Reminder Not Running?
Fix weekday reminder failures fast by validating cron expression, timezone, destination, and proof-of-next-runs.
Community pattern: users try to automate daily market/economic reminders, then assume cron is broken when jobs fire in the wrong place, wrong timezone, or on unexpected days.
Reality check: most "cron failed" reports are routing/timezone mismatches, not scheduler outages.
2-minute triage
- Confirm the job exists with a job ID.
- Confirm timezone (e.g.,
America/New_York).
- Confirm destination (DM vs server vs thread).
- Confirm schedule expression matches weekdays vs every day.
- Run one immediate canary reminder to prove delivery path.
Known-good weekday schedule
Schedule: 30 8 * * 1-5
Timezone: America/New_York
Meaning: 8:30 AM Monday-Friday (local New York time)
Copy/paste creation prompt
Create a cron reminder for weekdays at 8:30 AM America/New_York.
Message: "Reminder: Check today's economic calendar and share top 3 high-impact events."
Before finishing, return:
1) Job ID
2) Timezone
3) Cron expression
4) Next 3 run times (local + UTC)
5) Exact delivery destination
High-friction mistakes
- Heartbeat used for exact-time tasks: heartbeat drifts; cron is better for market-open precision.
- Wrong day set: using daily schedule when you wanted weekdays only.
- UTC surprise: one-shot schedules without timezone can be interpreted in UTC.
- Wrong destination: job fired to a different session/thread, so it looks "missing."
Canary test (always do this)
Create a one-time reminder for 2 minutes from now.
Message: "Canary reminder test"
Return the exact destination and fire time before finishing.
Loop-break rule: if two scheduled runs are missed, stop editing random settings. Recreate one clean job with explicit timezone + destination, then retest.
When to escalate to #help
- You have job ID + correct timezone + correct destination, but canary still fails.
- Runs history shows due executions but no delivered message anywhere.
- Runs consistently drift by 1+ hour after timezone is explicitly set.
Include: job ID, cron expression, timezone, next 3 expected runs (local + UTC), and exact destination.
Bottom line: for exact daily reminders, use cron + explicit timezone + destination proof on creation.