Confluence Automation Smart Values not working

[Rob Peters]

Hi, 

I have created the below automation in Confluence which add a template structure when a space is created of which the key starts with FM. The automation has been working perfectly but since this week it stopped working. Does anyone have experience with the situation? How can it be fixed? A similar issue also started with Jira Automation where the smart values conditions stopped working. 

Thanks. 

[Bill Sheboy]

Hi @Rob Peters 

How is the rule not working as expected?

For example, if the rule is not triggering...I wonder if this symptom is a racetrack timing problem, and that can happen when using the various "created <object>" triggers. 

For this reason, and others, I recommend never using the new feature to add conditions directly to triggers.  Instead, add separate conditions after the trigger. 

For Jira's Work Item Created trigger, an additional mitigation is adding the Re-fetch Work Item Data action immediately after the trigger and before any conditions.  Unfortunately, there is no equivalent of that action for Confluence objects yet.

Kind regards,
Bill

[Bill Sheboy]

@Rob Peters -- I am seeing this same symptom where the rule does not trigger now, and checking the status pages I do not see an open incident which might cause this.

As you are the Product Admin for a paid license, I recommend submitting a ticket to Atlassian Support to take a look.  When you hear back from them, please post what you learn to benefit the community.  Thanks!

https://support.atlassian.com/contact/#/

[Rob Peters]

Thanks guys for the feedback. I have taken the condition out of the trigger, but the strangest thing is that rules is not even triggered at all when a new space is created. Pretty frustrating.  

[Chris Rogers]

Hi @Rob Peters 

I suggest moving your condition out of the trigger and into a separate automation component.  I've found that conditions right on the trigger can sometimes be hit-or-miss, which may be what you're experiencing.

It might be a bit noisier in the audit log of the rule, but I suggest restructuring your rule as follows:

1. Space created trigger
2. Audit log of {{space.key}}
3. Condition for {{space.key}} starts with FM

That way, you'll be able to see that the rule is getting triggered, if there's an issue with the smart values that's tripping up the condition.