I have looked at some other NRF_ERROR_BUSY questions and the answers seem to be very dependent upon the situation and not necessarily 'busy' in the usual context of busy. In any case I am writing a pulse oximeter peripheral and I get an NFR_ERROR_BUSY sometimes when I try and indicate the resonse to an RACP transaction. The RACP transaction is transferring stored measurements (in this case just one) and the measurement actually gets transferred. But then I need to indicate the conclusion of the transaction to the central client. But I can sometimes get this NFR_ERROR_BUSY response. I am not sure why ( continuous measurements and some spot measurements are also being indicted and notified). Should I just try again? What are the chances this error will repeat ... and maybe forever?
Interesting: The client gets the response anyways in spite of the NRF_BUSY_ERROR. Which means the client gets more than one if I wait and retry. What am I to make of that?