Empty variable used

Check ID	MF_0003
Category	Quality
Summary	It is common when creating microflows to check for empty variables, attributes, objects or associations. If your logic expression or decision output is configured incorrectly (E.g. the output of the logic is true if the object is empty, but then you try to use the same object after the decision), it is possible to generate a runtime exception by accessing an empty object.
Options	This check does not have any options.
Pass	If your microflow checks for empty objects, it doesn't try to use those objects in the flows that come after the check.
Fail	If your microflow checks for empty objects, it uses those objects in one of the flows that come after the check.