Check-in reminders work only when I run the check-in manually
The check-in appears active in Dailybot, but participants do not get automatic DMs on schedule. When an admin clicks Run now (or the equivalent manual trigger), messages arrive. That usually means the schedule, workdays, or participant targeting is wrong — not that chat is completely broken.
Quick check
- Today is a workday for this check-in — Open Work days / calendar settings. Weekends, holidays, or “skip today” rules silence automatic sends.
- Participants are active — Deactivated or wrong chat accounts are skipped. Compare the participant list with people who actually received the manual run.
- Schedule timezone and send time — Confirm morning in the org timezone is not still “tonight” in the participant’s zone (see Check-in not open yet).
- Bot can DM participants — If manual run reaches everyone, DM permissions are probably fine; focus on schedule and roster.
- No org-wide pause — Rare maintenance or migration windows pause automatic jobs; manual runs may still work.
Common causes and fixes
Workdays or frequency exclude today
A check-in set to weekdays only will not auto-send Saturday/Sunday. A bi-weekly or monthly cadence skips off-cycle days. An admin may have added a holiday blackout. Open the schedule and work-day configuration and confirm today is included.
”Adapt to user work start time” delays the window
When a check-in uses per-user work start time, reminders open when each person’s workday begins in their timezone — not necessarily at 9:00 org time. A participant in Europe may not be “open” until their morning while US colleagues already responded. That is expected behavior; document it for the team or switch to a fixed org time if everyone should start together.
Participants missing from the automatic roster
Manual runs sometimes target “all active members” while the saved participant list is narrower. Reconcile the participant list with @mentions or teams used in chat. Re-save the check-in after edits.
Check-in marked active but schedule disabled
UI can show legacy status while the cron trigger is off. Edit the check-in, toggle schedule off and on, set the next send time a few minutes ahead, and save. Watch one participant account for the automatic ping.
Platform-specific delivery delays
Slack Enterprise, Teams policies, or Discord rate limits can delay bursts. If manual run works instantly for the same users, schedule is still the prime suspect; otherwise capture timestamps for support.
If none of this worked
Collect:
- Check-in name and screenshot of Schedule, Work days, and Participants
- Timezone shown on the check-in vs a affected user’s profile timezone
- Whether Run now always works for the same users who miss automatic sends
- Platform (Slack, Teams, Discord, Google Chat) and approximate times (with timezone)
Contact Dailybot support from the Help or Contact options in the product or on the website.