Repository navigation
Coach alerts: document the hourly cap on email and push - #64
Merged
Merged
Conversation
The portal guide, the Coach API and the Claude connector describe hourly_cap: on by default at one email and one push an hour per athlete, urgent alerts included; 1 to 12 an hour or off; held alerts go out together, none dropped; in-portal and webhook never limited; presets keep it; a full-replace write that leaves it out clears it at that scope. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Ci-From: linux Ci-Session: 1cf6b5b8-7b0a-4233-8f51-be4880ee968a
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.
What changes for a reader: the portal guide (Configuring alerts), the Coach API guide and the Claude connector guide describe the new hourly limit: on by default at one email and one push an hour per athlete, urgent alerts included; 1 to 12 an hour or off; held alerts go out together and none is dropped; in-portal alerts and webhook events are never limited; presets keep it; a full-replace write that leaves
hourly_capout clears it at that scope.Publish only after fuel-backend #1691 is deployed (the docs describe its behavior). Automerge is off for that reason.
Alex (verbatim, 2026-10-05): "hrly cap with manual toggle controlled by coach to override or set their own hourly cap if the hourly cap is not already a coach-controlled setting."
🤖 Generated with Claude Code