In this article, you will learn how to detect, review, and resolve errors that may occur in your automations.

You will discover how to use the history to identify what failed, interpret the results, and prevent common errors.

If you or your team notice that an automation is not running correctly, use the History filters to find the execution and investigate what happened.

You can filter by:

The action could not run because of the following error: “Empty source fields prevent the data from being generated.” This happens when the system cannot perform a mathematical calculation, assign calculated dates, or create text containing variables because some variables have not been populated.

The automation did not run because the conditions were not met.

Review how you defined the condition; it may not reflect what you actually intended.

The action could not run because of the following error: “Empty source fields prevent the data from being generated.” This happens when the system cannot perform a mathematical calculation, assign calculated dates, or create text containing variables because some variables have not been populated.

One or more actions did not complete because of a configuration or data issue.

See the next section to learn how to correct or prevent this.

In this example, you can see that the condition was met. When the condition was configured, the opportunity value was set to be greater than 1,000 (“Operator” and “Expected value” in the image). The value in the record that triggered the automation is higher: 1,200 (“Current value” in the image).

The automation ran successfully.

Everything is working as expected!

When an error occurs, the system will automatically send you an email notification.

From that email, you can access the latest detected errors directly and review the details to correct them.

🟩 You can add more recipients (internal users or external email addresses) from the automation settings. You can also disable notifications if you prefer.

A common error is:

“Empty source fields prevent the data from being generated.”

This happens when an automation attempts to perform a calculation or create text using empty fields. This prevents the system from completing the calculation or creating the text.

Suppose an automation calculates the “Number of rooms” field as the sum of “Single rooms” + “Double rooms”.

Imagine that a colleague wins an account (trigger), but does not populate the “Single rooms” or “Double rooms” fields. When the automation is triggered, the system will be unable to calculate “Number of rooms”. The following error will appear in the history: “Empty source fields prevent the data from being generated.”

Add a condition beforehand to ensure that the required fields are populated.

Use the Has data operator for the relevant fields so that the action only runs when information is available.

🟩 Example:

Suppose an automation calculates the custom field “Number of rooms” as the sum of the fields “Single rooms” + “Double rooms” (action).

A condition has been added to ensure that the source fields are populated, using the Has data operator for “Single rooms” and “Double rooms”. This means that “Number of rooms” will only be calculated when the fields are populated.

Make the source fields mandatory in the relevant entity.

This way, the system will require them to be completed whenever a record is created or modified, preventing errors in future automations.

If you cannot resolve the error after reviewing the conditions or settings, contact the support team.

Include the following in your request:

With this information, the team can help you identify and resolve the problem quickly.