DATA_TYPE_MISMATCH on Make.com: The scenario stops with an error message stating "The operation failed with an error: Type mismatch: expected [type] but got [type]" inside the module inspection bubbles. — Root cause: This error occurs when a module receives a data type that does not match what its backend field schema expects, such as passing plain text into a numeric or boolean field. It usually happens when an upstream app changes its output format or a user maps an unparsed variable directly without data coercion. — If data type mismatches persist despite correct mapping and explicit function parsing, contact Make.com customer support through the Help Center. Provide your scenario blueprint JSON file, execution history logs showing the input and output bundles, and screenshots of the mo