Siri on Apple Watch cannot set timers or alarms after WatchOS 27 update

That isn’t expected behavior. Apple’s watchOS 27 guide still lists setting alarms and timers with Siri as supported. → Take action with Siri on Apple Watch - Apple Support

Since the Timer and Alarms apps work manually, I’d try resetting Siri rather than the Watch again. On the iPhone go to Settings > Siri (or Apple Intelligence & Siri) > Talk & Type to Siri, turn Siri off, then turn it back on. Restart both devices afterward. Apple specifically recommends that step when Siri isn’t working properly on Apple Watch. → If Siri isn't working on your Apple Watch - Apple Support

Also try the same “set a timer” request directly on the iPhone. If it works there but the Watch still says the Clock app isn’t installed, that points more toward a watchOS 27/Siri issue. I wouldn’t erase or unpair the Watch again at this point.

My watch Siri Timer commands were working just fine after I upgraded both to iOS 27. HOWEVER, after I enabled the Siri Beta, no joy.

I went into Settings | Siri on the phone and backed off to “regular” Siri from Siri AI (Beta), and watch Siri Timer commands are now working again.

I get that it’s a Beta, but doesn’t literally EVERYONE use voice commands on their watch to set timers?

Hope it gets fixed soon so I can have my cake and eat it too.

I had the same problem with my Ultra 3. I ended up erasing the watch and setting it back up as new. Working normally now.

I factory reset my watch to no avail. But, turning off the new Siri fixed my issues on both my watch and phone. Won’t be doing the new Siri.

While Siri sometimes worked on my Watch when I had Siri AI enabled, it was VERY slow and sometimes failed.

Being an impatient type, I disabled Siri AI and now when I Siri on my watch she responds quickly again.

Looking around the internet a bit more it seems that many people are having issues with Siri on the Watch if Siri AI is enabled.

Hope that Apple fixes this soon. I would like to enable Siri AI but not at the expense of most losing Siri on my watch.

Good luck.

If you're expecting Apple to magically fix your problem, I wouldn't hold your breath.

Reboot, restore, erase and set up as new are the 3 big steps in troubleshooting most technical problems. Odds are one of those will fix it. If not, contact Apple support.

i'm having the same issue with Siri beta, tried disabling, restarting both devices, then enabling siri, restarting devices, and the watch still won't set a timer or work with homekit.

"classic" siri works just fine immediately after toggling it on, no resets required.

bertie256 wrote:

I'm not exactly sure what you're trying to say about the people on Twitter and Threads having the same issue... We're not working as a large network of rage baiters making this up. Even though you seem to be dismissing it as much as possible, this is a real issue that is relatively widespread. And I am sure you know that backups don't restore everything and can take a very long time, even though you don't want to admit it. What counts as a long time might be up for debate, but there is no way you can claim it's quick and easy... And it still doesn't have a 100% chance of fixing the bug, as I am sure you understand. I can't believe I'm having to explain this to someone with 200,000 points on the Apple support forum.

Yes, it's easy and relatively quick to unpair and re-pair your watch. No, I don't care that you don't believe me and would rather argue than do any troubleshooting. I respect your right to make your own choices.

Best of luck.

Yeah, it very well could. Did you try reverting to a non beta version?

I have the same problem, and it can't set reminders for me either. All of the apps are on my watch and working fine, and Siri on every other device is also working. I tried turning Siri off and on again but that didn't work, and I'm not going to go through the hassle of resetting my Apple Watch because that probably won't work either. As for the official 'support' article, it hasn't been updated in years seemingly and has parts that are just not accurate anymore. The issue seems to be relatively widespread; there's a MacRumours thread about the issue which is already a few pages long.

bertie256 wrote:

I'm not going to go through the hassle of resetting my Apple Watch because that probably won't work either.

KiltedTim reported that it did work. And it doesn't take very long or require that you do much other than wait for it to finish. It's certainly worth trying. Or, you can just continue to live with the problem.

You should let Apple know what you're seeing:

Product Feedback - Apple

MacRumours has a very apt name.

Yes, it is a hassle. It's not an instant process, and it takes a long time to get everything set up like it was before. I have done it before to fix a different issue and it was, to put it politely, a nightmare. Plus, it didn't even fix the issue I was having...

From what I've read it's worked for one person, and another one or two have said it hasn't worked. At best it's a 50/50 chance, and I'm not wasting a few hours for something that doesn't have a 100% chance of working.

And as for MacRumours, I assume the comment about the name is to try and say they're exaggerating or something like that. I don't know. But I've seen other people talk about it on Threads and Twitter, and there's obviously a lot more that I haven't come across. This is a real issue that a decent chunk of people are having!

bertie256 wrote:

Yes, it is a hassle. It's not an instant process, and it takes a long time to get everything set up like it was before. I have done it before to fix a different issue and it was, to put it politely, a nightmare. Plus, it didn't even fix the issue I was having...

Unpairing and re-pairing doesn't require any additional setup. It's reading everything from your most recent backup. If it's a "nightmare" you're doing something wrong.

And as for MacRumours, I assume the comment about the name is to try and say they're exaggerating or something like that. I don't know. But I've seen other people talk about it on Threads and Twitter, and there's obviously a lot more that I haven't come across. This is a real issue that a decent chunk of people are having!

Well, if people are saying that on Threads and Twitter then it must be true. My error.

I'm not exactly sure what you're trying to say about the people on Twitter and Threads having the same issue... We're not working as a large network of rage baiters making this up. Even though you seem to be dismissing it as much as possible, this is a real issue that is relatively widespread. And I am sure you know that backups don't restore everything and can take a very long time, even though you don't want to admit it. What counts as a long time might be up for debate, but there is no way you can claim it's quick and easy... And it still doesn't have a 100% chance of fixing the bug, as I am sure you understand. I can't believe I'm having to explain this to someone with 200,000 points on the Apple support forum.