Repository navigation
Conversation
history.EnableHistoryReplicationRateLimiter now takes {Enabled, Scope}. Scope "all"
rate limits every history append made by replication, as the bool did. Scope
"openForceReplication" only rate limits appends for force replication tasks of running
or paused workflows, so live replication never waits. A bool value is still accepted
and means "all". An invalid value, including a missing or unknown Scope, disables the
rate limiter.
The workflow state replicator records whether a task is force replication and the
workflow status in the context at ReplicateVersionedTransition and SyncWorkflowState,
and the three append sites check the scope against it. SyncState refetches keep the
force replication flag of the task that triggered them.
jiechenz
force-pushed
the
jiechenz/scoped-history-replication-rate-limiter
branch
from
October 24, 2026 00:00
0ed5cd5 to
e579baf
Compare
This branch has not been 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
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 changed?
history.EnableHistoryReplicationRateLimiternow takes{Enabled, Scope}:all: rate limit every history append made by replication (same as the old bool, which is still accepted).openForceReplication: only rate limit appends for force replication of running or paused workflows.Why?
The rate limiter can only be turned on for all appends, and blocking live replication appends stalls the replication stream. Scoping it lets force replication of open workflows, which backfills full histories, be paced without touching live replication.
How did you test it?
Potential risks