Merge fields errors and warnings

Working with Merge Fields in Workflow Studio

This article delves into how to detect and resolve merge field errors and warnings within your flows. When configuring flows, you might encounter various errors and warnings related to merge fields. Errors, depicted by a red outline and exclamation symbol on the node, must be resolved to activate the flow. Warnings, indicated by orange guide text and symbols, suggest potential issues that could lead to operational failures but do not prevent flow activation. Recognising and addressing these alerts is crucial for the seamless execution of your flows.

What are 'Errors' and 'Warnings'

Before diving into specific error and warning messages, it's important to differentiate between the two:

• Errors: These are critical issues that will definitely cause failures on flow activation. Therefore, errors in your flow will prevent activation and must be resolved in order to allow activation.
• Warnings: Warnings, on the other hand, are cautionary. They indicate potential issues that may cause failures, but do not prevent flow activation. Warnings can be dismissed, but the risk something might go wrong will remain. Warnings should be addressed based on the potential impact.

Common merge field errors and warnings

Below is a table outlining common merge field errors and warnings you might encounter, along with explanations to help you understand and resolve them.

Error / warning message	What this means
Merge field {{ name }} in ‘input field’ is from a missing node.	The node referenced in the merge field path (node output key) has either been mistyped, or the node itself has been deleted.
Merge field {{ name }} in ‘input field’ does not exist (not defined).	The field referenced in the merge field path has either been mistyped, or does not exist. Use the merge field explorer to copy and paste available merge fields.
Merge field {{ name }} in ‘input field’ is from an unreachable node.	The node referenced in the merge field path (node output key) still exists somewhere in the flow, but is not reachable by the current node. Nodes can only reference merge fields from prior nodes that would have been part of a common experience (reachable nodes). The node could be on the wrong path, or in an unreachable position; e.g. ahead of the current node.
Merge field {{ name}} in ‘input field’ must not use {{ }} syntax.	The input field that the merge field has been used in requires fields to be referenced without handlebars syntax {{ }}. Remove the {{ }} from the merge field.
Merge field {{ name}} is not a supported value.	The merge field is referenced in a node that does not support this type of merge field. Merge fields referencing email attachments are currently only supported in the Outbound email node. Remove merge field.
Must use a merge field in 'input field'.	The errored input field only accepts merge fields (without handlebars syntax {{ }}). Anything that is not a merge field cannot be used in this field. Only use merge fields.
Must remove spaces in 'input field'.	The errored input field does not accept spaces on either end of the merge field. Check the input field and remove the spaces on either end of the merge field.
Merge field {{ name }} is malformed.	The merge field may not have correct {{ handlebars }} syntax (e.g. missing a brace) or there may be no field defined after the node output key. Check the braces. When the merge field with hyphens or full stop is manually typed out, it must have a square bracket to be valid. For example, {{inboundMessageTrigger.[user-id]}} .
Merge field {{ name }} in ‘input field’ may not exist (not defined).	A field or object portion of the merge field may be mistyped, or a provided sample payload in a previous node does not contain the field or object. Check your sample payloads.
Merge field {{ name }} in ‘input field’ may not exist (uses an array).	An array [] is used in the merge field and can have differing amounts of items depending on an individual experience. If an item in the list is referenced, but doesn’t exist for that experience, the individual experience will fail.
Merge field {{ name }} in 'input field' is an array.	The merge field is referring to an array [], which could result in the rendering of the merge field as unformatted and/or undesired values that are within the array. Refer to a field instead.
Merge field {{ name }} in 'input field' is an object.	The merge field is referring to an object, which could result in the rendering of the merge field as unformatted and/or undesired fields that are within the object. Refer to a field instead.
Merge field {{ name }} in ‘input field’ must use {{ }} syntax.	The input field that the merge field has been used in requires handlebars syntax {{ }} for the merge field to dynamically populate. If handlebars are not added, the merge field will appear as-is (the text with braces).
Merge field {{ name }} will remain as text.	The input field that the merge field has been used in does not accept the use of merge fields. The merge field will appear as-is (the text with braces). Remove the merge field.