My check-in report doesn’t post until end of day
Your team finishes check-ins in the morning, but the shared report or digest still shows up much later. That is usually by design: Dailybot often waits until the window you configured closes or until everyone who is expected to respond has answered.
Quick check
- Report timing — Open the check-in settings and confirm when the report is set to compile and post. Many teams choose “end of day” so partial answers do not spam the channel.
- Missing responses — If the report is configured to wait for all participants, one late responder keeps the whole batch open until they submit or the deadline passes.
- Timezones — Verify each participant’s timezone in profile or personal settings and the org default. “End of day” follows those clocks, which can look like an evening post for some people.
- Frequency and cutoffs — Weekly or custom schedules can have a cutoff that does not match when you mentally “finished” the standup.
- Quiet hours — Some orgs delay outbound messages so they do not fire during local night hours; that can push the visible post later.
Common causes and fixes
Report timing set to compile at end of day
Check-in owners can choose when Dailybot rolls up responses into a channel post or email. If you selected end-of-day compilation, the report will not appear at standup time even if everyone answered early. That reduces noise when people straggle. To change it, edit the check-in schedule and reporting options so the summary goes out after a shorter window or on a fixed clock time. Communicate the change so the team knows when to expect the digest.
Not all responses are in yet
When “wait for all” (or similar) is enabled, Dailybot holds the report until the configured participants submit or until the deadline. If one person is out or forgot, the rest of the team sees nothing until they do. You can relax the rule to post after a percentage, after a time, or exclude optional participants. You can also send a nudge from the check-in dashboard for pending people.
Timezone misconfiguration
If the org default timezone is wrong or a member’s personal timezone does not match where they work, reminders and report cutoffs shift. Someone in London on an org default of US Pacific may see a report that feels like it belongs at the end of “their” day but is actually aligned to another region. Ask affected members to set their timezone in Dailybot profile settings. Admins should confirm the organization timezone under org settings. After changes, watch one full cycle to confirm the new behavior.
Channel or integration delays
Rarely, the chat platform queues or rate-limits messages so a post arrives slightly after Dailybot sent it. If timestamps in Dailybot show “sent” on time but Slack or Teams shows a lag, compare with a second test check-in. Persistent lag across platforms points to the chat vendor or network path, not the schedule itself.
If none of this worked
Before contacting support, gather:
- Check-in name and whether you are the owner
- Expected vs actual post time with timezones for you and one other participant
- Screenshot of schedule and reporting settings (no secrets)
- Whether the report is missing for everyone or only some channels
- Steps you already tried from this article
Then contact Dailybot support from the Help or Contact options in the product or on the website.