Repository navigation
fix(stats): keep scheduled collectors within separate request budgets - #96
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
ftw-webapp | dffbf41 | Commit Preview URL Branch Preview URL |
Oct 17 2026, 03:11 PM |
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 hourly stats run collects six repository snapshots and seven site-traffic days before reaching Cloud. A normal six-repo run can consume all 50 external requests, so the two public Cloud collectors fail immediately. The daily run also combines snapshots and traffic, which can exhaust the same budget.
Give each source group a separate schedule: repository snapshots at minute 3 hourly, public Cloud and site traffic at minute 23 hourly, and GitHub traffic alone at 00:17 UTC. Daily traffic no longer repeats repository snapshots. No billing tier or request limit changes.
A regression runs all three schedules for six repos, including a paged Core issue list, with fetch refusing request 51. It verifies 43, 9 and 24 external requests respectively and successful records for all 15 sources. Worker types and all 25 Worker tests pass; the Worker dry run passes. Verify the next real Cloudflare scheduled event before calling the deployed pipeline current. The existing page still retains its last valid installation estimate and never substitutes zero for missing energy.
Follow-up to #50. Household hourly collection remains disabled pending the separate privacy decision. Cloudflare documents the per-invocation limits at https://developers.cloudflare.com/workers/platform/limits/#subrequests.