FINERACT-2570: Defer webhook/hook event publication to after transaction commit in batch requests with enclosingTransaction=true#5719
Open
rhopman wants to merge 1 commit intoapache:developfrom
Conversation
Contributor
Author
|
Looks like the CI is failing because of an infrastructure issue. Can someone take a look and maybe re-run the checks? |
DeathGun44
reviewed
Mar 31, 2026
.../test/java/org/apache/fineract/commands/service/SynchronousCommandProcessingServiceTest.java
Outdated
Show resolved
Hide resolved
b1af246 to
76365cb
Compare
…ion commit in batch requests with enclosingTransaction=true
76365cb to
c899011
Compare
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.
When a batch request uses enclosingTransaction: true, Fineract fires hook events (webhooks) inside the database transaction, before the batch has fully committed. If a later request in the batch fails, the entire batch is rolled back, but the webhook for the earlier (now rolled-back) request has already been dispatched.
This causes downstream systems that rely on webhooks (e.g. SMS notifications) to act on events that never actually persisted.
Checklist