Ensure the automation is configured to use the trigger condition: Deal status has changed to won instead of a general condition like "Deal updated." This ensures that the trigger is specific and executes immediately.

You can also add more specific conditions to narrow down automations. For example, include on which stage the deal will be won and/or if they will have specific labels.

Automations don’t recognize imported deals as triggers. To enable automation for imported deals, manually modify the deal (e.g., change its stage) to activate the trigger.

Alternatively, you can use integrations, APIs, or set workflows to process updates incrementally, ensuring compliance with trigger conditions.

Items created via third-party web forms or API requests will be considered inputs by our automation tool as long as there‘s an automation that matches the corresponding trigger and its conditions. (E.g. If you have an automation that adds a label to your deals when they’re created, and then you create a deal using an API request, the label will still be added to that deal.)

Automation may fail for deals or contacts created with pre-filled fields through form submissions. Ensure such field values are edited or updated post-creation to activate the automation.- Automations in Pipedrive do not trigger on contact import events. After importing contacts, perform a real field update (e.g., modifying a label or a specific field) on imported records to fire the automation. Bulk edits can be used to achieve this efficiently.- If multiple actions, such as deal creation, stage updates, and custom field updates, occur simultaneously, the required field change might not be recognized by the system, and the automation will not trigger. Leave at least a 2-second gap between these actions to ensure they are processed as distinct events.

Automations only trigger based on changes made after they are activated. If a change (e.g., stage update) occurred before the automation was live, it will not execute.

Ensure the pipeline and stages selected in the automation match the deals you want them to work on. For instance, having similar stage names in different pipelines (e.g., "Contact Made") can cause misalignment. Test your automations with a test deal to confirm functionality.

Verify your email address is synced

Check if the sender email is linked with a valid person type field.

Ensure the field contains a linked contact with an associated email.

Double-check that the automation is set to trigger when the stage specifically changes to the desired stage (e.g., "Deployment") rather than on unrelated updates.

Automations process conditions sequentially and do not wait for activity updates to complete. Create a separate automation triggered by Activity Completed events, specifying conditions like "Status changes to Completed AND Title contains XX."

OR"Incorrect logical connections like 'AND' vs. 'OR' can stop automations from triggering. Switch to 'OR' when appropriate to allow flexibility in meeting condition criteria. Always test changes to confirm intended execution.

Confirm if the condition criteria is set up accordingly (e.g. a deal can only be in one stage at time so when wanting to use different stages for the same automation make sure the right condition set is also used such as "or" in this case).

Ensure automation conditions involving text fields match the exact specified text, respecting case sensitivity. For example, a condition for 'MONTHLY' will not trigger with 'Business_Monthly_Trial' unless the case and text match exactly.

When the condition has “contains”; it’s a case-sensitive matter, so make sure that the condition matches letter by letter.

Is the automation triggers based on a filter check the permission – the filter needs to be visible to everyone. If the filter is in the condition and is marked as visible to the owner only, it will trigger only for the owner. Ensure that the filter is set to 'Shared' to allow access to all relevant users and the automation system.

With delay steps, we are not looking for conditions to be met, this condition is used to pause this automation for a specific amount of time.
Delay is purely time-based and ensures the automation waits for a fixed period. It's meant to be used when you need fixed intervals between actions.

It's important to check when conditions are met or unmet.
​Example: Say that I want to delay it for 7 days, and it should continue the automation at 10am. On that 7th day at 10am the automation will continue to the next step.

General slowness

If user talks about general slowness; it's important to ask if general troubleshooting was done and guide the user to perform the steps as explained here: https://support.pipedrive.com/en/article/how-do-i-clear-my-browser-s-cache-and-cookies

Access the automation history log (Automations > History) to identify failures.

Look for executions marked with an 'X' and click to see the error message. For instance: - If the message under the "to" field says "[Value will be deleted]," it indicates a missing recipient email address in the linked contact. - Navigate back to the contact or deal to ensure an email address is associated.

Executions that don’t meet the conditions’ criteria will be discarded and not shown in the execution list.

Filter by Automation name from the dropdown and/or search for the name to filter.

Filter by the user who executed the automation. It will display all the list of all users for users with Global Admin permissions, otherwise it will only show the user themselves.

Refresh the history page.

Filter by last execution date.

Filter per Execution status.

Status of the specific automation.

Item that refers to the trigger event of the automation.

Name of the automation.

When the automation was last triggered.

How many steps the specific automation has.

Owner of the automation.

Stop execution button for automations with Wait for Condition and Delay steps.

Specify Accurate Conditions: Use precise triggers like Deal status changes to [stage].

Test Before Implementing: Use test deals or activities to ensure the automation triggers as expected.

Check Pipeline and Stage Consistency: Ensure the pipeline and stage align between the automation configuration and live data.

Maintain Linked Data: Verify that all fields, especially those essential like email or recipient fields, are filled correctly.

Monitor Automation History: Regularly review the history log for error analysis and troubleshooting.- Debug Sequentially: Ensure required actions occur sequentially with detectable gaps to allow the automation system to process each event.

Verify Condition Criteria: Double-check that all automation conditions, including nested rules, are precisely met.

Filter Accessibility: Ensure automation filters are configured to be visible and accessible to all participating users.