docs(email-reports): Cloudflare's cron weekday is offset by one - #23
Open
lamminpaa wants to merge 1 commit into
Open
docs(email-reports): Cloudflare's cron weekday is offset by one#23lamminpaa wants to merge 1 commit into
lamminpaa wants to merge 1 commit into
Conversation
The example config told readers `0 8 * * 1` means "every Monday at 8:00 UTC". On Cloudflare it fires on Sunday. Established rather than assumed. flarelytics-reports has run this exact expression since its last deploy on 2026-03-30, and all six reports between 2026-07-19 and 2026-08-23 landed on a Sunday at 08:00 UTC — confirmed independently by the sending API's own log, which also shows no send on Monday 2026-08-24 despite covering that morning. A GitHub Actions workflow in a sibling repo using the identical `0 4 * * 1` runs on Mondays, so the difference is the scheduler, not the expression. The schedule itself is untouched: which day the report arrives is a product decision, and it has been arriving on Sundays for months.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The example config told readers
0 8 * * 1means "every Monday at 8:00 UTC". On Cloudflare it fires on Sunday.How this was established
Not inferred from documentation — measured three ways.
flarelytics-reportsdeployment history0 4 * * 1Same expression, same field, different day. The difference is the scheduler.
So:
1= Sunday on Cloudflare,2= Monday.What this changes
Only the comment. The schedule stays
0 8 * * 1, because which day the report arrives is a product decision and it has been arriving on Sundays for months — silently matching nobody's stated intent, but matching the actual habit of anyone who reads it.If Monday is wanted, that is a one-character change to
0 8 * * 2, worth making deliberately rather than folding into a docs fix.🤖 Generated with Claude Code
https://claude.ai/code/session_01X8eThbPu42vk7AcFstqaRB