A formerly successful/validated rule was working fine a week ago. Now, it doesn't show up at all on the audit log, so it's not a matter of it being wrong.
I created a new simple logging automation with the trigger "When page is moved" to test it, but it doesn't show up either. Only the config change appears.
Is the automation service currently down?
Hey @ana.faustino ,
In the meantime there seems to have been an issue raised at Atlassian regarding slowness of Automation:
https://jira-service-management.status.atlassian.com/incidents/hbhx13fzvdgz
Great, thanks for the information! I'll subscribe to this issue and see if anything updates on my end.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the community.
You need to check the audit log of Confluence, not the audit log of the automation rule.
So you need to go in the administration of Confluence and check the audit log there.
In the log of the automation rule, only information on the automation rule is kept.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I will need to contact our admin, as I don't have access to the administration section. I will update once I can see either the Confluence audit log or the the space audit log. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @ana.faustino , how confident are you in the fact that the associated event actually resulted in a trigger of the rule? I have not personally used page moved as a trigger before. It certainly could be that there has been a regression and a recent update to your instance. I will try the page moved trigger and let you know what I see later today.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As you can see by the screen shot, "Move page" as a trigger was working fine last week. "Publish page" as a trigger was also working.
Tomorrow I noticed both rules were not resulting in the updated labels, and when checking the audit log of the automations it didn't have anything new.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @ana.faustino , from what you have conveyed, it all seems very straightforward and as you have experience with it working previously, I am suspicious of a regression. Please do open a support ticket with Atlassian and let us know what they find.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I did a quick test and also found that the event did not trigger.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.