feat(listeners): implement idempotent restart from persisted cursor#608
Merged
Baskarayelu merged 1 commit intoJun 27, 2026
Merged
Conversation
|
@afeezorobsco-cyber Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
|
implement idempotent restart from persisted cursor — clean work, in it goes 🚀 |
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.
##close #575
Description
This PR implements idempotent restart behavior for the Horizon Bond Creation listener by restoring the last persisted cursor on startup instead of always starting from
now.On startup, the listener loads the saved
paging_tokenfrom the existinghorizon_cursorstable usingCursorRepository. If no checkpoint exists or the lookup fails, it safely falls back tonow, preserving the existing cold-start behavior.Changes
nowwhen no checkpoint exists or the lookup failsThis implementation is additive, introduces no schema or configuration changes, and aligns the bond creation listener with the existing restart behavior used by the other Horizon listeners.
Closes #