Adding a nullifying condition ensures your automation runs only once. You can do this by setting a condition that becomes false after the automation runs.
For instance, if your automation action increases ticket priority to urgent, set it to run only on tickets with high priority. This way, once the priority is changed to urgent, the condition is no longer met, stopping the automation from running again. Alternatively, use tags by adding a tag to the ticket and setting the automation to look for tickets without that tag. This ensures the automation only runs once per ticket.
This error occurs because your automation lacks a nullifying condition. Essentially, your automation needs a condition that tells it when to stop running. You can fix this by either adding a nullifying condition or by creating a trigger instead. To…
Use a trigger instead of an automation when your conditions are not time-based. Triggers are better suited for actions that need to happen immediately when certain conditions are met. If you find that your automation is causing errors because it…
Nullifying conditions ensure your automation runs only once by making a condition false after the automation runs. One example is using ticket priority: if your automation increases priority to urgent, set it to run only on tickets with high…