Skip to content
Troubleshooting Member Admin

My check-in reminder fires at the wrong time

My check-in reminder fires at the wrong time

Quick check

  • Personal timezone — Set your timezone under Dailybot Settings > Profile (or personal preferences) to the city that matches your current work location, not your headquarters.
  • Organization default — If you never set a personal timezone, Dailybot may use the org default. Admins can see and adjust the default under organization settings. Members who travel or work remotely should still set personal timezones.
  • Daylight saving transitions — Twice a year, reminders shift with local law. If only one person is wrong, it is usually their profile timezone. If everyone is wrong by one hour, inspect the org timezone and any template-level schedule definition.
  • Compare schedule UI to chat timestamp — Open the check-in schedule screen and note the stated send time next to the timezone label. Compare with the timestamp on the actual message in Slack or Teams. Small differences help support narrow the bug vs misconfiguration.

Common causes and fixes

Personal timezone not set (org default applied)

New accounts sometimes inherit the org HQ timezone. If you work several zones away, reminders arrive early or late. Set your personal timezone explicitly. Wait for the next scheduled send to confirm. Admins should communicate that remote employees must set this field — it is not automatic from the chat platform in every setup.

Daylight saving time (DST) edge cases

Regions that observe DST change effective offsets. Well-configured systems follow IANA zones (for example, America/New_York) and adjust automatically. If someone chose a fixed-offset label incorrectly, spring and fall jumps look like product bugs. Switch to a named region timezone instead of a raw UTC offset when the UI offers both.

Check-in schedule timezone vs personal timezone

Templates can be authored in one timezone and interpreted with another layer for members. When both are visible in the UI, they should tell a consistent story. If the template is fixed to “9:00 org time” but your personal setting is ignored where you expected a shift, read the field help on the schedule screen or ask an admin whether the check-in is meant to be org-synchronized or localized per user. Adjust expectations or settings accordingly.

If none of this worked

Before contacting support, collect:

  • Your Dailybot profile timezone string as shown in the UI
  • The check-in name and screenshot of its schedule configuration including any timezone labels
  • A screenshot of the chat message with visible timestamp
  • Whether the issue started after a travel or DST weekend
  • Organization name

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

Want to go deeper? See the Dailybot Academy for global team scheduling practices.