Bots & Messaging blog

Article

Send a weekly digest on the recipient's clock

A scheduled digest needs a clear local delivery time, a stable identity for each issue and a record of what happened when it was sent.

Define which Friday you mean

Suppose a team wants a Telegram digest every Friday at nine in the morning. Store the team's named time zone, weekday and local time. Calculate the next occurrence using that zone. If colleagues in another office subscribe to a separate digest, give that subscription its own schedule. A fixed UTC hour can shift on the local clock when daylight saving changes.

Record the issue before dispatch

Use the subscription and intended local date to identify a weekly issue. Save its reporting window and the content prepared for delivery. If two scheduler instances wake up together, a uniqueness rule in storage lets one claim the issue. Check that the subscription is still active before sending. Record the provider's message identifier when available so support can trace a specific dispatch attempt.

Test the awkward week

Use sample dates either side of a daylight-saving change and compare the local send time and reporting window. Pause the worker over Friday morning, restart it, and check your chosen catch-up rule. For example, an editor may prefer a late digest on Friday and no digest on Saturday. If the provider times out after receiving a request, flag the uncertain outcome for reconciliation. Repeated sends can otherwise give readers two copies of the same issue.

All articles and case studies Describe your workflow