If you have a microflow that a scheduled event uses you cannot add parameters to that microflow, even if those parameters are optional and contain a default value. Clearly these parameters are not truly optional if the scheduled task cannot figure out that it does not need to provide any values for them. To this extent, scheduled events should support microflows that have optional parameters since that what optional means.
In the current implementation developers are forced to create duplicate microflows just so they can manually call the same microflow but with an optional parameter, which is bad design.
Hi Alex,
I agree, I have seen this exact same behaviour elsewhere.
If I have a mf with an optional object param with default empty.
Then call it from a page that also has the object optional empty, then open the page without passing the object, the mf call button is permanentntly disabled.
I need to create 2 page variations, one which has the page param and one without.
Really annoying!