Whenever we create automation do we need to check it after some time that it is working correctly or we need to update it after some time and if we need to check or update then why ?
Hi, @Anurag Vipin Vaidya
You can check if it’s working, if you’d like - but it’s not mandatory. Usually, if something goes wrong, you’ll receive an email notification that the automation has failed.
From my experience, I regularly review the global automations and check the audit logs for all rules. This helps me spot any failures early and fix them promptly.
@Evgenii Okay Understand but why it gets failed
There could be a large number of reasons, such as:
@Evgenii Suppose i am working on a project and i am active daily expect sat-sun Then also is there any chances to get automation fail
Hi @Anurag Vipin Vaidya
Adding to the suggestions from @Evgenii ...
Although automation rules can send emails when something causes an error, that will not indicate all possible automation problems:
Regarding Atlassian outages, for many of the possible rule triggers, there is no guarantee that the rules will run to "catch up" on all missed executions. This depends upon the type of event, licensing level, etc. A good defensive practice is to fully understand what each of your rules does, why it does it, and how that might be mitigated if the rule does not run. (For example, using a manual or scheduled trigger rule to perform the "catch up" for missed executions.)
Finally, please consider: teams create automation rules to solve some need, automating repeatable work. And so a team needs pay attention to that work happening (or not) to monitor their rules' health.
Kind regards,Bill
It looks like you're new here. Sign in or register to get started.
