This KB explains why resynchronization with network jobs is not triggered after an update or deploy operation from the Security Director (SD) Cloud UI, and how resynchronization works in SD Cloud.

Resynchronisation with network jobs will not trigger after update/deploy job from SD cloud UI.

Resync job will be triggered from syslog notification of the device to SD Cloud via the below configuration set as part of adopt device.

set system syslog file sdcloud-messages match "(UI_COMMIT_COMPLETED)|ifAdminStatus|ifOperStatus|(FRU power)|(FRU removal)|(FRU insertion)|(link UP)|(vc add)|(vc delete)|transitioned|Transferred|transfer-file|(license add)|(license delete)|JSRPD_HA_HEALTH_WEIGHT|PKID_PV_CERT_LOAD|PKID_PV_CERT_DEL"

set system syslog file sdcloud-messages structured-data

the syslog must have a entry of “UI_COMMIT_COMPLETED” post commit of first deploy job in that SRX device. 

Note: As long as the syslog message is received for the commit on the SRX device, resync will be always triggered over SD cloud UI

The only possibility for missing the resync is that the syslog message is not published from the device for that specific commit towards SD cloud.  If rsync job is not triggered over SD cloud UI under job management then we need to capture the logs under “sdcloud-messages” file under /var/log folder of the affected SRX device for further investigation.