Automation Information ?

[Anurag Vipin Vaidya]

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 ? 

[Bill Sheboy]

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:

• a configuration change could alter the rule behavior, including by not limited to changes with: product licensing, users, work item type, custom fields, rules deleted / disabled, etc.
• an Atlassian outage impacting products and / or automation, which may be monitored by frequently checking (and subscribing for updates) here: https://status.atlassian.com/
• a larger scale, internet outage, which may be monitored with your ISP and news sources

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

[Evgenii]

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.

[Anurag Vipin Vaidya]

@Evgenii Okay Understand but why it gets failed 

[Evgenii]

There could be a large number of reasons, such as:

• Deactivated users
• Permission issues
• Changes in workflows
• Incorrect conditions or actions in automation rules that don't fully align with requirements
• etc...

[Anurag Vipin Vaidya]

@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

[Evgenii]

The reasons I listed above can happen at any time - and you might not even be aware that something has changed until the automation fails.

For example, a user who was previously assigned by default to certain issues in a project may leave the company, and their account could be deactivated. This change would then break any automation relying on that user’s active account.

If your rule is configured to send emails about failures - you will receive information about problem very quickly. But if you disabled it - it’s important to proactively monitor automation health and update rules as needed.