One of our manually-triggered Flows has required Parameters, but they aren't behaving like a required Parameter. One would expect that if a required Parameter received a null, that the Flow would fail to execute, and an error be displayed in the calling Flow's 'Run a Child Flow' Action, right? (That's Q1.)
Instead, the called Child Flow is executing, and then failing where the parameter is used. And, given that it's required, there's no code trapping for the null value. Are we now expected to edit every single Child Flow and add error trapping for required parameters? (That's Q2.)
Have I gone mad, or is this new behavior? (That's Q3) I've created child flows for over 4 years now, and never remember this being the case.
Q1. Shouldn't a flow without properly supplied required parameters fail to even execute and an error be displayed within the Calling Flow?
Q2. Is this new behavior?
Q3. Is the remedy really to add error trapping to every single child Flow?
P.S. The Categories below are 100% worthless.
Share
Report
784
All responses (
Answers (
