ble_db_discovery_start returns NRF_ERROR_BUSY for previously bonded devicehttps://devzone.nordicsemi.com/f/nordic-q-a/24372/ble_db_discovery_start-returns-nrf_error_busy-for-previously-bonded-deviceI am working off the ble_cts_c example, using SDK 14.0.0, SoftDevice S140, and nRF52840. All works well when I pair a device for the first time: the nRF discovers services on the central device. When I reset and connect to a previously bonded deviceen-USTelligent Community 13Wed, 16 Aug 2017 16:43:09 GMTRE: ble_db_discovery_start returns NRF_ERROR_BUSY for previously bonded devicehttps://devzone.nordicsemi.com/thread/95949?ContentTypeID=1Wed, 16 Aug 2017 16:43:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c778f58b-2a2d-4e6d-af60-66e037955058Petter Myhre<p>Strange. Have you checked where the error originates from? Is it from this?</p> <pre><code>if (p_db_discovery-&gt;discovery_in_progress) { return NRF_ERROR_BUSY; } </code></pre> <p>or from somewhere else? Also, maybe <a href="https://devzone.nordicsemi.com/question/111845/parallel-db-dyscovering-services-for-several-connections/">this</a> is of interest.</p><div style="clear:both;"></div>