https://devzone.nordicsemi.com/f/nordic-q-a/67833/nrf52832-s132-v6-1-1-race-condition-with-ios-phy-update-to-2-mbit-s-when-slave-latency-is-enabledHello, We&#39;re making RuuviTag sensor beacons which log environmental data to flash. Logged data is later read by a mobile phone application over Nordic UART Service. The log read flow goes like this: Mobile phone connects to RuuviTag Mobile phoneen-USTelligent Community 13Mon, 02 Nov 2020 10:47:19 GMThttps://devzone.nordicsemi.com/thread/278022?ContentTypeID=1Mon, 02 Nov 2020 10:47:19 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f9787466-856f-4aeb-919f-726001fe0d69Kenneth<p>Hello,</p> <p>I am not aware of any issue no, in general I have seen in the past (with various peers) that initiating procedures on connected event have a tendency to trigger race conditions in the peer. The typical solution is to add a 100ms delay or more before&nbsp;requesting the procedures, this may be as simple as a fixed nrf_delay_ms(100); before sending the request on connected event. It would be interesting to see if this impact the problem in any way.</p> <p>I think to get further an on air sniffer log would be helpful (e.g. using nRF sniffer should be possible).</p> <p>Best regards,<br />Kenneth</p><div style="clear:both;"></div>