Your Zendesk automation might stop firing due to the restrictive nature of the 'Hours since | Is' condition. Automations run every hour, but not necessarily at the top of the hour or at the same time each hour. For instance, if a ticket was assigned 5 hours ago at 10:03, and the automation fires at 15:01, the ticket was only assigned 4 hours and 58 minutes ago, so the condition isn't met. If the next automation fires at 16:06, the ticket was assigned 6 hours and 3 minutes ago, and the condition fails again.
To resolve this, consider using 'Hours since | Greater than' for a broader time window. Remember to define a nullifying condition or action to ensure the 'Greater than' condition is true only once per ticket. For more details, check out the originalZendesk help article.
To fix Zendesk automation issues related to time conditions, switch from 'Hours since | Is' to 'Hours since | Greater than'. The 'Is' condition is very precise and can easily miss the exact time window needed for the automation to fire. By using…
The 'Hours since | Is' condition in Zendesk automations is a time-based rule that triggers actions when a specific number of hours have passed since a ticket event. However, it's very precise and can lead to missed triggers if the automation…
Using 'Hours since | Greater than' in Zendesk automations provides a more flexible time window for conditions to be met. Unlike the 'Is' condition, which requires precise timing, 'Greater than' allows the condition to be true over a broader range…