Repository navigation
fix(social): retry the schedule three times a day, post once - #87
Merged
Merged
Conversation
GitHub ran the 15:00 cron five hours late on Oct 6 and not at all by 18:00 on Oct 7, so the first tweet missed its day. The schedule now fires at 15:17, 18:17 and 21:17 UTC (off the busy :00 minute), and a scheduled run posts nothing when a tweet already went out that UTC day. Manual `post` runs still post right away. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
GitHub's cron is best effort: the
0 15 * * 1-5run started at 20:03 UTC on Oct 6 and had not started by 17:53 UTC on Oct 7, so #51 missed its slot. It was posted by hand with apostdispatch.:17avoids the top of the hour, when GitHub delays scheduled runs the most.postrun is not limited.Tested with
checkand three mocked runs: scheduled with a tweet already out today posts nothing; scheduled with the last tweet on an earlier day posts; manual posts even after today's tweet.Touches
social/post.mjsandsocial/README.mdnext to #86, in different lines.🤖 Generated with Claude Code