New "This component may be incompatible" error on automation

[Rees_ Ian]

Recently a few of my automations that have always worked before, now produce a "This component may be incompatible" error when the rule is updated.  However, the rule still runs successfully so I can ignore the error. I have simplified the rule down to as shown i.e. trigger when a version is created then create an issue in the triggering project.  Why has this suddenly started producing an error when it was ok before

[Trudy Claspill]

Hello @Rees_ Ian 

Referencing @Bill Sheboy 's response on this post:

https://community.atlassian.com/t5/Jira-questions/Automation-error-This-component-may-be-incompatible/qaq-p/2746714

...the introduction of that warning message is described here:

https://community.atlassian.com/t5/Automation-articles/New-Improvements-for-Jira-and-Confluence-Automation/ba-p/2744140

He also noted that he has encountered false-positive occurrences of that warning.

I created a rule using the same two components as you and did not get the warning, so you may be encountering a false positive occurrence.

[Trevor Angle]

Hi @Rees_ Ian, this is Trevor from the Confluence automation team. I saw your post and flagged it with the automation team in charge of Jira components, and they confirmed that this is a bug. I believe they've released the fix now, so hopefully you should stop seeing this incorrect validation warning!