3023423 - Synchronization automatically triggered with forceUpdate by "Synchronize" action in Backoffice

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

Triggering synchronization with ForceUpdate flag enforces synchronization of every item in source catalog version regardless of whether target items require update or not. In some cases number of unnecessarily synchronized items can be counted in hundreds of thousands or even in millions. Such synchronization can takes hours instead of expected minutes.

Below property was introduced into 'backoffice' extension in project.properties file around CX6.3, but it's not documented in help.sap.com documentation. It has ability to affect setup of forceUpdate flag in created synchronization cronjobs.
backoffice.sync.config.forceUpdate=true

It's purpose is to set forceUpdate flag to true as default value for synchronizations triggered from backoffice by "Synchronize" action (circling arrows icon ) on Catalog Version item.

This setup may lead to accidental startup of long running synchronization cronjob since full synchronization with forceUpdate always synchronizes all items between catalog versions defined in sync job. 

All Commerce Cloud with backoffice (since CX6.3.0.6)

syncjob update long stuck synchronization  synchronize forceUpdate backoffice.sync.config.forceUpdate backoffice.sync.config , KBA , CEC-SCC-PLA-PL , Platform , Problem