New type of async business rule from Rome onwards - async_always. [async (deprecated: not run during upgrade)]

[Daniel A-C]

async (deprecated: not run during upgrade)
This async rule is deprecated as it will NOT run during upgrade. It is recommended that you switch to the new 'async' option.

I'm opening this thread to try to gather more information about this new annotation found on business rules in a Rome instance. The docs aren't particularly detailed and I find this message confusing. One of my colleagues interpreted this to mean that existing async rules won't run ever again after upgrading the instance to Rome and I must admit I had to read it a few times to get the idea.

Looking into it; I can see the choice values are now: 

The new entry's value async_always would seem to suggest that these business rules will continue to be able to run, subject to actually being triggered in their normal way and having their conditions met, regardless of whether there is an upgrade currently in progress. I interpret this to probably mean any upgrade including hot fix, patch or family version but not plugins, update sets or app installs. (Would be great if anyone can confirm this?)

I will refer to these as value:async (the old one) and value:async_always (the new one) for the rest of this post to avoid confusion.

Does anyone know if this is because...

1. Prior to Rome, value:async business rules didn't run whilst an upgrade was in progress
   or
2. From Rome onwards, a change has been made and value:'async' business rules no longer run whilst an upgrade is in progress?

The Rome release notes for Core Platform say:

Core Now Platform highlights for the Rome release: Create async business rules that run automatically.

Important information for upgrading Core Now Platform to Rome: To avoid breaking a workflow, when you don't select the necessary async business rules to run during an upgrade. Newly created async business rules run automatically on an upgrade.

Where would you be selecting which async business rules to run during an upgrade? I don't think I've ever seen a prompt for that. Also this sentence is pretty hard to understand and could do with revision in my opinion.

Can anyone offer any more background information on how/why this change has been made?

Thanks in advance

[Lorenzo Persich]

Can you try with this alternate link? I tested in in an incognito Chrome session and it is opening ok for me.

[Michael Domke]

Thanks for new link. Yes, I am able to view it now. Much appreciated.

[rita_m]

Hi Lorenzo - 

The KB is not available to everyone. When I try to view it I get "Your role does not grant you access to this article. Please use Search to find related content."  This is AFTER logging in.

From reading through all the comments on this post, I'm not the only one who had this issue.

Could you summarize it, please?

Thanks!

[Lorenzo Persich]

Please check the alternate link I pasted in additional comments. It works for me in an incognito window.

[kristinacree]

I was looking at the same thing, there are SEVERAL of these that area created by SNOW that is still on that older async (deprecated: not run during upgrade). I don't want to adjust their records, but is that going to cause issues? i can adjust all our created items but worried about the number of theirs that could break.