Bugfix: Fixed NullPointerException on Flow Logging Actions - #1021
Merged
jongpie merged 4 commits intoAug 25, 2026
Conversation
…ger shows the per-parameter include toggles There is recent-ish change in Salesforce Flow Builder that removed the per-input "include this parameter?" toggles, which now causes Flow to always send every optional input. Boolean inputs now come across as null, instead of using the default values assigned in the Flow classes. The Flow actions have been updated to expect & handle null for Boolean values.
jongpie
temporarily deployed
to
Advanced Scratch Org
August 24, 2026 18:56 — with
GitHub Actions
Inactive
jongpie
temporarily deployed
to
Experience Cloud Scratch Org
August 24, 2026 18:56 — with
GitHub Actions
Inactive
jongpie
temporarily deployed
to
OmniStudio Scratch Org
August 24, 2026 18:56 — with
GitHub Actions
Inactive
jongpie
temporarily deployed
to
Base Scratch Org
August 24, 2026 18:56 — with
GitHub Actions
Inactive
jongpie
temporarily deployed
to
Platform Cache Scratch Org
August 24, 2026 18:56 — with
GitHub Actions
Inactive
jongpie
temporarily deployed
to
Event Monitoring Scratch Org
August 24, 2026 18:56 — with
GitHub Actions
Inactive
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1021 +/- ##
==========================================
- Coverage 94.19% 94.19% -0.01%
==========================================
Files 58 58
Lines 6517 6511 -6
Branches 204 204
==========================================
- Hits 6139 6133 -6
Misses 376 376
Partials 2 2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
jongpie
temporarily deployed
to
Base Scratch Org
August 24, 2026 19:19 — with
GitHub Actions
Inactive
jongpie
temporarily deployed
to
Base Scratch Org
August 24, 2026 19:37 — with
GitHub Actions
Inactive
jongpie
deleted the
bugfix/flow-builder-removed-per-input-include-toggles
branch
August 25, 2026 15:38
Owner
Author
|
This has been released in release |
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.
Fixed #997 NullPointerException that occurs when Flow passes a null value for the optional inputs
Save LogandThrow FlowException for Fault Error Message, which happens now that Salesforce has removed the per-input include toggles from the Flow Builder action panel 😐tl;dr - Salesforce broke stuff (╯‵□′)╯︵┻━┻