DRU-484: Schedule usage polls with idle backoff - #488
Open
czpython wants to merge 2 commits into
Open
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
czpython
marked this pull request as ready for review
September 8, 2026 19:34
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
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.
Usage snapshots stop updating when no Usage page is open. Add
core.refresh_usagewith a fixed five-minute schedule so connected subscriptions update without a browser.UsageScrape.is_due()polls first-time subscriptions and subscriptions with a completed call after the last scrape. A completed call takes priority over an exhausted snapshot. Otherwise, an exhausted window waits for its earliest reset. A window reset makes one poll due.Unchanged quota values increase the interval through 5, 10, 20, 40, and 60 minutes. One interval table sets the history limit and delay. The
quotaproperty compares the error tag, five-hour percentage, and weekly percentages in provider order. Only changed quota values restart the interval. Manual refresh retains its 60-second floor.The task reloads each subscription before a poll. Session expiry and revocation during a tick do not break later polls. The schedule is a code constant, consistent with the current
@taskcontract. No schema or frontend changes are required.Validation
uv run ruff check backendanduv run ruff format --check backendpassed.uv run pytest backend/passed: 1,744 tests.Closes DRU-484.