When setting priority low for connection event and scan priority to high, the scan window gets interrupted every time when there is supposed to be a connection event.
However, the connection event did not happen due to the priority set in the application layer which is expected.

The ideal solution should be that scan windows does not get interrupted when its priority is set to high and connection priority is set to medium unless the existing connections hit 1/2 supervision timeout.

Root Cause:
This issue occurs due to the scheduler cutting off the scan end time to prioritize a connection event to prevent a timeout.

Fix:
Additional logic was added to the scheduler to ensure a higher priority secondary task executes to completion only if doing so will not result in a connection timeout.