.. _cuc-schedules:

Schedules
.......................

Configuring a CUC device on Automate creates a scheduled
data sync to import model data from the device into Automate. 

The scheduled data sync ensures that the VOSS Automate cache maintains
the most current view of the configured device. 

.. note::

   If Holiday Schedules were added to CUC directly, update the default scheduled
   data sync instance to include the Model Type List called ``CUCXN Schedules`` in order
   to ensure that these holiday schedules are synced into VOSS Automate.


Any changes to the configuration occurring on the device,
including additions, deletions, or modifications, reflect in VOSS Automate
after the next data sync.


.. note::

   * There is no immediate data sync upon update or modification.
   * Some license-related models will now be excluded from Cisco Unity Connection
     imports by default:
  
     * ``device/cuc/Handler``
     * ``device/cuc/GlobalUser``
     * ``device/cuc/LicenseStatus``
     * ``device/cuc/TenantUserLicense``
     * ``device/cuc/UserLicense``

The recurring sync (disabled by default) is scheduled to occur every 14 days. You can enable 
the sync and modify the schedule (via **Apps Management > CUC > Schedules**).

When determining the appropriate schedule setting, the frequency of the sync must be
weighed against the additional processing and network activity associated with
the data sync. You can manually run the data sync at any time, 
via **Apps Management > Advanced > Perform Publisher Actions**, or from **Administration Tools > Data Sync**.

.. important::

   Allow the initial data sync to complete before doing more configuration on
   Automate that requires information from CUC.

The performance of a data sync can be improved by controlling the types of data
that are synced. 


.. rubric:: Related Topics 

* 
  .. raw:: latex
  
     LDAP User Sync in the Core Feature Guide.

  .. raw:: html

     <a href="set-up-ldap-user-sync.html">LDAP User Sync</a>