Repository navigation
Promotion lease: due posts first, re-checks rotate - #29
Merged
Merged
Conversation
…tch of 20 A post myna holds for weeks (every network here is at its daily cap until Nov 1) was re-leased ahead of newly due posts, so more than five of them would have starved the calendar. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Found live: every myna network here (LinkedIn, Bluesky, Mastodon) is at its 12/day cap until about Nov 1, so campaign posts sit in
scheduledfor days. The lease ordered byplanned_atwith a batch of 5, so once more than 5 posts were scheduled it would only ever re-check those and never hand myna the newly due ones. Now due posts come first, re-checks go least-recently-checked first, and the batch is 20 (max 50). There is a test.🤖 Generated with Claude Code