I'm working to set up a few automations on spaces to help with knowledge lifecycle management, some of which rely on changes to statuses. I had previously tested automations which, when a page status was changed (e.g. to "Ready for review"), would kick off Slack/email notifications, and do some labeling.
However, these seem to no longer work all of a sudden. I've confirmed that the issue doesn't lie with the automation itself, I've built some super simple ones, for example:
IF Page Status changes to "Ready for review"
THEN Add Label "test-success"
This automation no longer works, but if I change the IF condition to IF Add Label "label-ready-for-review", the automation fires as expected. Ditto for the Slack and Email ones, so I'm confident it's not an issue with webhooks, etc.
I strongly suspect that this issue is caused by a teammate and I changing around the space statuses - both adding custom ones, and removing some defaults (likely multiple times... nobody uses statuses currently so we didn't see an issue messing with them for now).
Is it possible to confirm that changing statuses at the space level can break these automations, even if we've since changed them back? I've gone to space settings > content statuses > Restore defaults, but still find that a simple automation that should fire when a page's status is changed to "Verified" no longer works.
I am having a similar problem. All of a sudden my label automations are not applied; they do not even register as the rule failing. Is this a bug in Confluence?
We didn't remove the status from the page.
Hi @craig_scott and welcome to Community!
Could you be impacted by one of these bugs?
Hope this helps!
- Manon
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.