Synchronization Timeout

Learn to troubleshoot synchronization timeout error.

Time-consuming single requests can occur during data synchronization.

All offline datasets in a request are queried during incremental synchronization base on a timestamp (the time of the last incremental synchronization). The server, therefore, only needs to check a small number of records and usually reacts within a short time period.

If timeout problems occur during incremental synchronizations (e.g. after many records were changed), carry out a full synchronization. If this problem occurs regularly, increase the request timeout.

Several requests are submitted one after another during a full synchronization:

• The first request transfers the complete application configuration, data model and catalog data to the client.
• The offline datasets that are synchronized are determined in CRM.designer. A request is submitted for each offline dataset, i.e. the full request timeout period is available for each offline dataset.

If problems occur during the first request, increasing the request timeout can help (although up to date no such cases are known). If the problem occurs while synchronizing one of the offline datasets, there are several options available to solve the problem. For further details, see Full Synchronization Terminates Due to the Timeout.

If you increase the timeout intervals, take into account that long synchronization requests result in a high load on the database server. Users are confronted with delays. Therefore, apply the other optimization options, in particular optimizing access rights and the database.

Change Requests after Client Timeout

If a Save request cannot be carried out due to a client timeout, the request is stored on the device.

All change request that occur after a client timeout are not carried out until the next UpSync is carried out.