OOB Business Rule AgentNowResponseProcessor (ACC-F) still using legacy async value — should be migrated to new async option - Known Error

OOB Business Rule AgentNowResponseProcessor (ACC-F) still using legacy async value — should be migrated to new async option Description The OOB Business Rule AgentNowResponseProcessor (sys_id: 700a3507670b3300b7b72dbd2685ef32), owned by the Agent Client Collector Framework (ACCF) application, is currently set to the legacy async value (async — deprecated: not run during upgrade).

Per KB0951770, starting from the Rome release, ServiceNow introduced a newer async behavior (async_always) that creates sys_trigger records with upgrade_safe = true, ensuring async BRs execute during upgrades.

Existing pre-Rome async BRs were intentionally not auto-migrated at the time for backward compatibility reasons. However, this OOB BR has not been updated to the new async option in any subsequent release through Zurich.

Customer has raised a valid question on why ServiceNow's own OOB code has not been updated per its own platform-level recommendation. Request is to evaluate migrating this BR to the new async option so it runs during upgrades and aligns with current best practice.

Steps to Reproduce

Open the BR in any OOB instance where ACC-F is installed : https://<>.service-now.com/nav_to.do?uri=sys_script.do?sys_id=700a3507670b3300b7b72dbd2685ef32

And you will see the information message as in when to run tab :

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

Workaround Please import the attached update set .