https://devzone.nordicsemi.com/f/nordic-q-a/26697/how-to-deal-with-this-race-conditonI&#39;m using nRF52832, soft device 2.0, SDK11 and as a central. When it happens I&#39;m scanning for peripheral to connect. Usually it&#39;s a peripheral advertises at very low rate, ie only a few times per second and with very weak RSSI, ie around -90dbm. en-USTelligent Community 13Tue, 14 Nov 2017 02:01:21 GMThttps://devzone.nordicsemi.com/thread/104994?ContentTypeID=1Tue, 14 Nov 2017 02:01:21 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c7061bd1-9f2e-4244-af47-556f3325435abluebeam<p>thanks for the advise. I think it works a lot better now.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/104993?ContentTypeID=1Wed, 08 Nov 2017 22:43:40 GMT137ad170-7792-4731-bb38-c0d22fbe4515:05857e7c-f336-41b7-bcd0-e21709ec99e6RK<p>just set the scan timeout to whatever time you want to wait for connection. You&#39;ll either get a connection callback or you&#39;ll get a connection/scan timeout callback. Then you can retry or not depending on what it is you&#39;re trying to do. If you always wait for one or other callback, you know you are in a good state all the time, no race condition.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/104996?ContentTypeID=1Wed, 08 Nov 2017 22:22:52 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3ba70c02-0954-4229-b36a-e46c59c3d453bluebeam<p>I haven&#39;t thought about that. Then I&#39;ll set my scan timeout to be 1 sec and restart every second?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/104995?ContentTypeID=1Wed, 08 Nov 2017 00:29:17 GMT137ad170-7792-4731-bb38-c0d22fbe4515:20fb2443-d31a-44a2-949f-807b915a48a1RK<p>why don&#39;t you just put the timeout into the scan parameters of the connect call instead of having a separate one and trying to cancel. That&#39;s what that parameter is there for.</p><div style="clear:both;"></div>