Enable project synchronization across all execution nodes, ensuring that every node maintains the same Git commit revision regardless of where the sync was initiated.

• If the execution node is changed in the Job Template at launch time, the job should fail if that node has an older project revision than the current synced version.

Customer would not need to enable update revision on launch, which currently forces a project sync on every launch and can delay job execution.

As a workaround, we have provided steps to add a cache timeout on a project trouch api and set the value for "scm_update_cache_timeout"