Troubleshooting template display issues in a flow

When managing automated flows, you may sometimes run into situations where an outdated template loads in a flow or dynamic data doesn’t populate correctly. These issues are usually related to template updates or incorrect use of variables.

Let’s talk about how to fix template display issues in your flow.

An old template version is being sent

In SendPulse, emails and email templates in an automated flow are different objects and don’t sync automatically. That’s why it’s important to keep templates in your flow up to date.

If you edit a template in Email > Templates, emails that are already in your automated flow will remain unchanged and continue sending the previous version. To avoid this, update emails directly in your flow.

If you edit an email in your automated flow, these changes won’t apply to the original template.

If you update a template before the Email element is executed, all contacts that are already queued in this element will receive the new version instead of the old one.

Variables from a contact source are not being substituted

Email variables pull data from sources linked to your flow:

• event that triggers your flow;
• contacts from a mailing list, if it’s selected.

If you use variables, make sure they exist in at least one of these sources.

If a variable exists both in the event and the mailing list, the system uses the value from the event. Mailing list data points act as a fallback and are used only if the corresponding field wasn’t passed in the event.

Besides that, make sure the variable name syntax in your template matches the syntax in your contact source exactly. For example, if a variable is named City in your mailing list, use City in your template, not city.

Data from the array is not being added

If you pass dynamic data into an email body using an array, make sure the variables are inserted correctly. Verify the following:

• The item is included in your variables, for example, {{item.price}}.
• The event that triggers the flow provides the same data used in the email.
• All required tag attributes are included, such as src for images and href for links.

Read more: Send data arrays with Automation 360.

Information is not being added to a webhook

You can send tracked events, such as email opens, to external systems. In this case, the system expects only the keys and the format specified in the Action: Send webhook element settings.

If the response includes additional custom variables along with the expected key, or if the response structure changes, the webhook is considered invalid.

Last Updated: 12.01.2026