Asynchronous Operation Replay allows users to submit changed data outside a synchronization session without waiting for EIS execution. When an application calls submitPending on an MBO on which a create, update, or delete operation is performed, an operation replay record is created on the device local database.
When synchronize is called, the operation replay records are uploaded to the server. The method returns without waiting for the backend to replay those records. The synchronize method downloads all the latest data changes and the results of the previously uploaded operation replay records that the backend has finished replaying. If you choose to disable asynchronous operation replay, each synchronize call will wait for the backend to finish replaying all the current uploaded operation replay records