Troubleshooting automations
If an automation behaves unexpectedly, find your case below.
Triggers
The trigger fired in an unexpected order or didn't fire
Queue triggers run one after another, so the result of one trigger can affect another. Check the trigger order. To find out whether a trigger fired in a specific issue and whether its actions failed, see the trigger history.
Trigger conditions are met in unexpected ways
Several triggers can run in a single issue update. A user's comment can start a trigger that adds another comment. If another trigger responds to comments, Tracker can consider both comments when checking its conditions.
For example, suppose you set up a trigger that responds to new comments and added two conditions:
- Comment author → Field value isn't equal to → Anna.
- Comment author → Field value isn't equal to → Boris.
You expect the trigger to ignore comments from Anna and Boris. But when Anna posts a comment, another trigger adds a comment on behalf of Boris. Both comments are part of the same issue update.
Tracker checks each condition separately. Boris's comment matches the first condition, and Anna's comment matches the second. Both conditions are met, so the trigger runs.
The trigger doesn't change the issue status
The transition may be blocked by the permissions of the user whose change fired the trigger, or by required fields on the transition screen. For more information, see Changing issue status.
The trigger doesn't create an issue
An issue isn't created if the trigger fires in an issue that was already created by automation. For more information, see Creating an issue.
The trigger doesn't close the parent issue
The cause may be permissions for the parent issue, an incompatible combination of conditions, or a delay in updating related issues. For more information, see Close a parent issue after closing all subtasks.
Auto actions
An auto action updated only some issues
An auto action processes only the first 100 issues that match its conditions each time it runs. The remaining issues are processed the next time it runs. Learn more about setting up auto actions.
The auto action doesn't change the issue status
The auto action is run by the robot yndx-tracker-cnt-robot@. The transition may be blocked by conditions that restrict user permissions for changing the status, or by required fields on the transition screen. Add the robot yndx-tracker-cnt-robot@ to the list of users allowed to make the transition, and check that the transition screen has no required fields. For more information, see Changing issue status.
The auto action doesn't create issues on schedule
Issues are created by the Yandex Tracker robot. Make sure that it has permission to create issues in the queue where the auto action is configured. For more information, see Schedule creating issues in Yandex Tracker.
Macros
Only one macro changed a field when you ran several macros
If several macros change the same field, the last macro you selected takes effect. To get the value you want, select the macro that sets it last. Learn more about running macros.