Flow Designer does not enforce validation of the Action Output Variables's mandatory flagIssue When configuring output variables in Flow Designer Actions, marking a variable as mandatory does not enforce validation in the same way as it does for input variables.SymptomsIf a Flow action defines an output variable as mandatory but does not provide a value for it during execution, the flow does not throw an error or halt execution by default. This can lead to confusion, as one might expect the flow to error out when a mandatory output is not populated. However, the platform currently does not enforce the requirement for mandatory outputs in this context.ReleaseSince the release of the Flow Designer.ResolutionWhat is the purpose of the mandatory flag on output variables in Flow Designer Actions? The mandatory flag on output variables is primarily informational and editorial. It serves as guidance to the designer or developer using the Action in a Flow, indicating that a particular output should be provided by the Action logic. However, the platform does not enforce this flag at runtime — if a mandatory output variable is not set during execution, the flow will continue without error. This is different from input variables, where the mandatory flag is enforced at design time and prevents the Action from being saved or run without the required input being supplied. How can I enforce mandatory outputs if needed? If your business logic requires certain outputs to be guaranteed, you can implement your own checks, like: In the Action itself, make the value mapped to the output field non-empty.Or use logic/action in the Flow after running the custom action to check if the action output is empty.