Thanks for the updates, we’re seeing the same kind of “misfire / immediate threshold reach” behavior reported by our users as well (blocked even when they haven’t used the app yet), so it’s helpful to know it’s still reproducible on the latest 26.4 betas. Could you share how you reproduce it reliably? What schedule / threshold configuration are you using? Does it happen right after starting monitoring, after a reboot, or after an OS update? Any pattern around downtime / always-allowed / exempt lists? Device model + exact iOS build (e.g., 23E5223f) when it reproduces? Any concrete steps would be greatly appreciated.