https://devzone.nordicsemi.com/f/nordic-q-a/39192/softdevice-v6-scan-pause-specificationAccording to the documentation of the softdevice v6. The scanner will automatically stop in the following cases: sd_ble_gap_scan_stop is called. sd_ble_gap_connect is called. A BLE_GAP_EVT_TIMEOUT with source set to BLE_GAP_TIMEOUT_SRC_SCANen-USTelligent Community 13Mon, 08 Oct 2018 10:20:41 GMThttps://devzone.nordicsemi.com/thread/152003?ContentTypeID=1Mon, 08 Oct 2018 10:20:41 GMT137ad170-7792-4731-bb38-c0d22fbe4515:bc8a740f-8cb9-4816-8ef7-a8cc21426ed0run_ar<p>Well, there is no guarantee. It is a trade off, and necessary to give the chip some time to access the received data. As you pasted originally: <em>&quot;In this case scanning is only paused to let the application access received data.&quot;</em>.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/151866?ContentTypeID=1Fri, 05 Oct 2018 14:55:22 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b6323bc3-56d0-485b-9ecc-b307dff7d1b6mich_x<p>Yes, exactly. This is why I have some concerns about this? If you automatically stop the scan and depends on the program to restart it, then how does it guarantee that the scanning will not miss the next possible beacon?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/151812?ContentTypeID=1Fri, 05 Oct 2018 11:20:55 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7cbb2979-d7d8-4072-923d-a37c31f5cd60run_ar<p>Hi,</p> <p>As far as I know this is implementation specific. I.e. previously (before v6 api) it was not necessary to restart scanning when a ble_gap_evt_adv_report event was received.</p><div style="clear:both;"></div>