Sync Ops Status for CMDB CI Business Rule runs after insert/update with a current.update(), causing recursion - Known Error

Sync Ops Status for CMDB CI Business Rule runs after insert/update with a current.update(), causing recursion Description Business Rule 'Sync Ops Status for CMDB CI' runs after insert/update and contains a bad-practice current.update() statement which causes recursion.

Depending on what else the transaction is doing, in relation to other OOTB and custom business rules, including the CI to Asset synchronization, symptoms may include fields not getting updated as expected.

Steps to Reproduce

OOB Business Rule 'Sync Ops Status for CMDB CI' that is an after/insert update BR which contains a current.update() statement which is indicating recursion. This BR is showing that we are spending majority of the time just processing.

Here is a snippet of the transaction from a customer when this BR is executed. We can clearly see that there is recursion.

2020-10-28 08:45:11 (951) worker.1 worker.1 txid=31eabc031bc0 Recursive business rule call for 'Sync Ops Status for CMDB CI' on cmdb_ci_dns_name: xxxx is being ignored. Business Rule Stack: Sync Ops Status for CMDB CI,Sync Ops Status for CMDB CI 2020-10-28 08:45:04 (288) worker.5 worker.5 txid=caea3c831b84 Recursive business rule call for 'Sync Ops Status for CMDB CI' on cmdb_ci_dns_name: xxxx is being ignored. Business Rule Stack: Sync Ops Status for CMDB CI,Sync Ops Status for CMDB CI Workaround This problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.

The fixed Quebec version of this business rule runs before update, without a current.update().