Sleep shortcut leaves orphan alarm after cancelling sleep tracking

[salomaocohen]

Hello Sleep as Android team,

I’d like to report a serious UX issue related to sleep shortcuts (e.g. “Sleep 8 hours”) that can easily cause unintended wake-ups.

What happens

1. I tap a sleep shortcut such as “Sleep 8 hours”.
   • Sleep tracking starts.
   • A real alarm (with smart window) is created.
2. I then pause/cancel/delete the sleep tracking session.
3. The app silently keeps the alarm active.

Result:
The user reasonably assumes everything was cancelled, but the alarm still fires later, waking them up at an unexpected time.

Why this is a problem

• From a user perspective, sleep tracking + alarm are perceived as a single action.
• Cancelling the sleep tracking strongly implies cancelling everything created by that action.
• There is no warning, no confirmation, and no indication that an alarm remains armed.
• This behavior already caused me to be woken up at the wrong time.

This is not user error — it’s a misleading mental model created by the UI.

Suggested fixes (any one would help)

• When cancelling/deleting sleep tracking started via a shortcut, ask whether the associated alarm should also be deleted.
• Or automatically delete alarms created by shortcuts when the tracking is cancelled.
• Or clearly show a warning like: “Sleep tracking stopped, but the alarm is still active.”

The app is technically excellent, but this UX edge case is very easy to fall into and has high impact.

Thank you for your work and for considering this report.

Best regards,