A real person reads it. Routine Run is a small operation, so expect an answer in a day or two rather than an hour.
Bugs get fixed first
The team is working through bug reports actively and ships each fix as soon as it is ready, not saved up for a big release. Every build and what it fixed is on Changes.
What to include
Enough that the first reply can be an answer rather than a question back:
- What you were doing, and what happened instead.
- The name of the routine or step it happened on, if it was a particular one.
- Your iPhone model and iOS version, and the watch too if it happened there.
- A screenshot, when the thing is easier to show than to describe.
Please do not send anything you would not want in an email. Nothing is required beyond the above, and a routine's contents are rarely needed to work out what went wrong.
Setting it up with a paging app
Starting a runbook when PagerDuty, Opsgenie, incident.io or Sentry pages you is a Shortcuts automation, and it has a page of its own: Start a runbook when you get paged. It also lists what each line in History › Decisions means when nothing happened.
Something you wish it did
Worth sending, and worth saying what you were trying to get done rather than which button you want. The second is easy to add and often the wrong fix for the first.
Your data
Routine Run keeps everything on your device and collects nothing, so there is no account to recover and nothing of yours held anywhere we could look. That also means support cannot see your routines — whatever you describe is all we have to go on. The privacy policy has the detail.