fix: Flush fields for logic rule actions#1584
Merged
trebitowski merged 2 commits intomasterfrom Mar 24, 2026
Merged
Conversation
joondotcode
approved these changes
Mar 23, 2026
0431df7 to
0755996
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.
Changes
Flushes field changes before feathery client actions. This ensures that the calls to the BE use the most recent field values, even if the field and client action are in the same logic rule (and/or in a loop). This is a common pattern used with other actions, but these ones were not flushing fields.
Before, we were not flushing values, which meant actions like sendEmail would not have the correct field values.
Example:
https://feathery.slack.com/lists/T014564UQA2/F09GD42JFU4?record_id=Rec0AN0T0Q5U4
Checklist before requesting a review
Related pull requests
Link other PRs here that are related to this change