Failures usually generate a specific error or reason visible under the Execution History tab. To help me pinpoint the problem, please let me know what error is currently showing in the History page.
To find your automation history, go to Automations > History.
Common automation errors
Below are common errors and what they mean:
State | Title | Message |
| Maximum frequency limit reached | Maximum automation execution frequency limit reached. |
| Invalid data | There was a problem with the data used in the automation execution. |
| Inactive user | User is inactive. |
| Unidentified execution error | Something went wrong. |
| Insufficient permissions | The user executing the automation doesn’t have sufficient permissions. |
| Maximum retry limit reached | Maximum number of automation execution retries reached. |
| Inactive company | Company is inactive. |
| Unidentified execution error | Something went wrong. |
| Invalid data | There was a problem with the data used in the automation execution. |
Maximum frequency limit reached or Maximum retry limit:
This is usually related to automations or email-api, for example. You can review the workflows to ensure an action in the automation isn't triggering the same automation again (e.g., an automation updates a deal field, which triggers a different automation that updates the same deal field). This limit is in place to prevent infinite loops and system overloads.
Invalid data: This error means that when trying to execute an action, some values were not valid. For example; the action is "Send email" and the "To" field was linked with the email field of the deal contact person, but that field is empty on the deal. You can review the Action step and ensure all required fields are populated and that the type of data being input matches the field type (e.g., currency goes in a currency field, dates go in date fields or if using merge fields ensure the source item has valid data in that field. An empty required field will cause this failure.
Inactive user data: Inform the that if the execution failed due to an inactive entity, which might include an inactive user or inactive company. Meaning the Pipedrive user who owns or created the automation is currently deactivated or the Pipedrive company account is currently inactive.
Unidentified execution error or Something went wrong: Inform the user that these are general errors that indicate an unidentified issue occurred during execution and that something went wrong on the Pipedrive side during processing. They can wait a few minutes and try triggering the automation again. Temporary connectivity or queue issues often resolve themselves.
Insufficient permissions: Inform the user did not have permission to execute the action. Please make sure the user trying to trigger the automation has full visibility to all items linked to the item being used to trigger. Example: The action is "Delete Deal" but the user trying to trigger the automation doesn’t have "Delete deals" permission. They can review User Permissions under Permission Sets and by checking the items triggered.
The automation is over the size limit: Inform the automation document size has exceeded the 100 kB limit. While the number of steps or fields used within an automation are not strictly related to overall document size, adding numerous option custom fields with extensive options increases the risk of surpassing the limit.
Say: Since there's no way to exceed or upgrade this size limit we advise you to check the automation and make the necessary adjustments to work according to the current limit size.