@@ -355,21 +355,21 @@ Troubleshooting
355355If the analysis of your schema times out, it might be because the
356356collection you are analyzing is very large, causing MongoDB to stop the
357357operation before the analysis is complete. Increase the value of
358- ``maxTimeMS `` to allow the operation time to complete.
358+ ``MAX TIME MS `` to allow the operation time to complete.
359359
360- To increase the value of ``maxTimeMS` `:
360+ To increase the value of :guilabel:`MAX TIME MS `:
361361
3623621. In the query bar, expand :guilabel:`Options`.
363363
364- .. figure:: /images/compass/schema-query-options .png
364+ .. figure:: /images/compass/max-time-ms .png
365365 :alt: The Options button is on the right side of the query bar,
366- next to the green Analyze button.
366+ next to the Analyze button.
367367
368- 2. Increase the value of ``maxTimeMS`` to accommodate your collection.
369- ``maxTimeMS`` defaults to 5000 milliseconds, or 5 seconds, but large
368+ 2. Increase the value of :guilabel:`MAX TIME MS` to accommodate your collection.
369+ :guilabel:`MAX TIME MS` defaults to 60000 milliseconds, or 60 seconds, but large
370370 collections might take tens of seconds to analyze.
371371
372- Once you have increased the value of ``maxTimeMS` `, retry your schema
372+ Once you have increased the value of :guilabel:`MAX TIME MS `, retry your schema
373373analysis by clicking :guilabel:`Analyze`.
374374
375375.. toctree::
0 commit comments