DOCSP-40390: Client max offline time can no longer be disabled (#809)

Client max offline time can no longer be disabled

Author: cbullinger

source/images/client-max-offline-time.png

@@ -7,10 +7,10 @@ Partition-Based Sync
 ====================
 
 .. facet::
-   :name: genre 
+   :name: genre
    :values: reference
 
-.. meta:: 
+.. meta::
    :description: Find information about the older sync mode for Atlas Device Sync, Partion-Based Sync.
 
 .. contents:: On this page
@@ -24,11 +24,11 @@ the older Partition-Based Sync. Partition-Based Sync has been deprecated and is
 disallowed for new Sync configurations.
 
 The information on this page is for users who are still using Partition-Based
-Sync. 
+Sync.
 
 .. note:: Migrate from Partition-Based Sync to Flexible Sync
 
-  We recommend migrating Partition-Based Sync apps to 
+  We recommend migrating Partition-Based Sync apps to
   Flexible Sync. For more information on migration, refer to :ref:`realm-sync-migrate-modes`.
 
 Key Concepts
@@ -358,8 +358,7 @@ Procedure
             - :ref:`Client Recovery <recover-unsynced-changes>`
 
             If you want to change the length of time that a client can be
-            offline, or disable either of these features, you can do so
-            in the :guilabel:`Advanced Configuration` section.
+            offline, you can do so in the :guilabel:`Advanced Configuration` section.
 
          .. step:: Turn On Sync
 

source/reference/partition-based-sync.txt

@@ -67,8 +67,7 @@ value of 30 days.
 
    Client maximum offline time enables trimming for
    older history. This permanently changes affected
-   history, and can cause client resets in the future even after
-   disabling the feature.
+   history and can cause client resets in the future.
 
 Key Concepts
 ~~~~~~~~~~~~
@@ -109,11 +108,7 @@ client reset. Existing history has already been changed by trimming,
 requiring a client reset. New history needs time to accumulate up to
 the new client maximum offline time.
 
-Disabling the client maximum offline time feature stops additional
-trimming, but history that has already been changed by
-trimming will permanently cause client resets in clients.
-
-Decreasing client maximum offline time also does not *immediately*
+Decreasing client maximum offline time does not *immediately*
 change the length of time before clients experience a client reset.
 Client resets begin taking place earlier once the regularly scheduled
 trimming job applies trimming to the newly
@@ -129,23 +124,21 @@ Set the Client Maximum Offline Time
    .. tab::
       :tabid: ui
 
-      1. Select the :guilabel:`Device Sync` menu in the sidebar.
+      1. From the App Services UI, click :guilabel:`Device Sync` menu in the
+         sidebar. The :guilabel:`Dashboard` tab displays by default.
 
-      #. Under :guilabel:`Sync Type`, make sure :guilabel:`Flexible` is selected.
+      #. Click the :guilabel:`Configuration` tab.
 
-      #. Scroll down to the :guilabel:`Advanced Configuration (optional)` dropdown.
-         Click the dropdown to open.
+      #. Scroll down to the :guilabel:`Advanced Configuration (optional)`
+         section, and click the dropdown to expand the section.
 
          .. figure:: /images/client-max-offline-time.png
            :width: 750px
-           :alt: The client maximum offline time configuration in a disabled state.
-
-      #. Under the :guilabel:`Client Max Offline Time` section, click
-         the :guilabel:`Enable Max Offline Time` toggle.
+           :alt: Advanced Configuration section in the App Services UI
 
-      #. Specify a number of days for your application's client maximum
-         offline time. The default value is 30 days. The minimum value is
-         1.
+      #. Under the :guilabel:`Client Max Offline Time` section, specify a number
+         of days for your application's client maximum offline time. The default
+         value is 30 days. The minimum value is 1.
 
       #. Click the :guilabel:`Save Changes` button at the bottom of the screen
          once you are ready to save.
@@ -251,8 +244,6 @@ Summary
 - Trimming reduces the space usage for Flexible Sync apps, but can cause client resets
   for clients who have not connected to the backend in more than
   the client maximum offline time (in days).
-- Flexible Sync apps that have disabled a client maximum offline time do not apply trimming,
-  so clients of any age can sync without experiencing a client reset.
 - Adding additional queryable fields to a flexible sync configuration
   will increase storage consumed on an Atlas Cluster. Using broad queries
   and selecting fewer fields that support broad queries decreases storage consumed.