Softdevice behavior during long interrupt using scheduler

[Rafig]

Hello, 

We have an app_timer that runs periodically for the application, and we are also using BLE peripheral code. Once the application timer expires, the event handler code takes around 200ms to execute (read sensor data, algorithm processing and etc.). Assuming that we are using scheduler both for the timer and the softdevice, what will happen if softdevice related interrupts get fired during this period? 

As I understand, the softdevice code that had to be executed inside the interrupts will be postponed into the next scheduler queue element. In other words, SD related activities will be delayed by 200ms. 

Below is graphical illustration for better understanding:

What will be the consequences of it? 

Is it safe to use it in this way?

What is maximum allowed time that we can spend inside scheduler element so that softdevice can work properly? 

[Turbo J]

Setup interrupt riorities properly, i.e. assign the lowest priority (highest number) to the RTC interrupt.

The timing sensitve softdevice interrupts run at high priority and will preemt your 200ms code path.

[Rafig]

Thank you for the reply. How can it preempt 200ms code if it is inside the scheduler?