[Backport axon-5.3.x] Document that the initial token is not a replay - #4983
Merged
Conversation
A streaming processor starting without a stored token handles its initial catch-up in ReplayStatus.REGULAR rather than as a replay. Document this behavior and the reasoning across the PooledStreamingEventProcessorConfiguration Javadoc, the streaming event processors reference page, and the projectors migration guide, including how to flag the initial catch-up as a replay when handlers rely on ReplayStatus.REPLAY to suppress side effects. (cherry picked from commit e3decfa)
github-actions
Bot
requested review from
MateuszNaKodach and
zambrovski
and removed request for
a team
August 27, 2026 06:24
smcvb
enabled auto-merge
August 27, 2026 06:24
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.
Description
Backport of #4982 to
axon-5.3.x.