This functionality is currently in beta and is available only for a small group of customers. It will soon be made available to the rest of the users.
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 went wrong, how to interpret the results and what to do to prevent common errors.
1. What to do if something is not working as expected
If you or your team notice that an automation is not running correctly, use the filters in the History to locate the execution and analyse what happened.
You can filter by:
Name of the automation, if you know which one may be failing.
Date, to check since when it has not been working.
Triggering user, if a specific colleague detected the problem.
Result, to review executions with the status Success, Filtered or Error.
Filtered
The action could not be executed due to the following error:
“Source fields are empty, preventing the system from generating the value.”
This occurs when the system cannot perform the mathematical calculation, the assignment of calculated dates or the creation of texts with variables because some variables have not been filled in.
What does it mean?
The automation did not run because the conditions were not met.
What to do?
Review how you defined the condition; it may not represent what you actually intended.
Error
The action could not be executed due to the following error:
“Source fields are empty, preventing the system from generating the value.”
This occurs when the system cannot perform the mathematical calculation, the assignment of calculated dates or the creation of texts with variables because some variables have not been filled in.
What does it mean?
One or several actions were not completed due to a configuration or data issue.
What to do?
Check the next section to learn how to correct or prevent it.
Success
In this example you can see that the condition was met. When the condition was configured, it was defined that the opportunity must be greater than 1,000 (‘Operator’ and ‘Expected value’ in the image), and the triggered record is greater, 1,200 (‘Current value’ in the image).
What does it mean?
The automation executed successfully.
What to do?
Everything is working as expected!
2. What to do in case of an error
2.1. Error notifications
When an error occurs, the system will automatically send you a notification email.
From that email you can directly access the latest detected errors 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.
3. How to prevent errors
Practical example of an error and how to prevent it
A common error is:
“Source fields are empty, preventing the system from generating the value.”
This happens when an automation attempts to perform a calculation or create a text using empty fields. This prevents the system from being able to complete the calculation or generate the text.
Suppose an automation calculates the field “No. of rooms” as the sum of “Single rooms” + “Double rooms”.
Imagine a colleague wins a company (trigger), but does not fill in the fields “Single rooms” or “Double rooms”. When the automation is triggered, the system will not be able to execute the calculation of the “No. of rooms” and will show in the history the error:
“Source fields are empty, preventing the system from generating the value.”
How can you prevent it?
Option 1 – From the automation
Add a pre-condition that ensures the required fields are filled in.
Use the operator “Has data” on the relevant fields so that the action only runs when information is available.
🟩 Example:
Suppose an automation calculates the custom field “No. 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 filled in, using the operator “Has data” on the fields “Single rooms” and “Double rooms”. This way, the calculation of the “No. of rooms” will only be performed when the fields are filled in.
Option 2 – From field configuration
Set the source fields as mandatory in the corresponding entity.
This way, the system will require them to be completed whenever a record is created or updated, avoiding errors in future automations.
Option 3 – If the error persists
If after reviewing the conditions or configuration you still cannot resolve it, contact the support team.
Provide in your request:
The name of the automation
The execution ID
The date and time of the error
With this information, the team will be able to help you identify and resolve the issue quickly.