You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can monitor a replication’s status by using a combination of <<lbl-repl-chng>> and the `replication.status.activity` property -- see; {url-api-enum-replicator-activity}.
242
242
This enables you to know, for example, when the replication is actively transferring data and when it has stopped.
When access to a document is removed on Sync Gateway (see: Sync Gateway's xref:sync-gateway::sync-function-api.adoc[Sync Function]), the document replication listener sends a notification with the `AccessRemoved` flag set to `true` and subsequently purges the document from the database.
320
320
--
321
321
322
+
[#lbl-repl-pend]
323
+
=== Documents Pending Push
324
+
325
+
TIP: {url-api-method-replicator-isDocumentPending} is quicker and more efficient.
326
+
Use it in preference to returning a list of pending document IDs, where possible.
327
+
328
+
You can check whether documents are waiting to be pushed in any forthcoming sync by using either of the following API methods:
329
+
330
+
* Use the {url-api-method-replicator-getPendingDocumentIds} method, which returns a list of document IDs that have local changes, but which have not yet been pushed to the server.
331
+
+
332
+
This can be very useful in tracking the progress of a push sync, enabling the app to provide a visual indicator to the end user on its status, or decide when it is safe to exit.
333
+
334
+
* Use the {url-api-method-replicator-isDocumentPending} method to quickly check whether an individual document is pending a push.
0 commit comments