Remoted throwing errors every day

Why is remoted throwing errors every day? This seems to have started a few days ago, and it happens every morning when I wake my MacBook Pro from sleep. I've been sending the problem report to Apple, but I'm worried about a serious bug. I think this is the relevant line in the report: ""termination" : {"flags":0,"indicator":"monitoring timed out for service","code":1,"namespace":"WATCHDOG","details":["(1 monitored services unresponsive): checkin with service: remoted (0 induced crashes) returned not alive with context:","is_alive_func returned unhealthy : device not responsive (code 0x4)","60 seconds since last successful checkin, 33267 total successful checkins since 355058 seconds ago"]}," and that it does not reveal any of my private information.

[Re-Titled by Moderator]

Original Title: Why is removed throwing errors every day?

MacBook Pro 16″, macOS 26.2

Posted on Feb 6, 2026 7:04 AM

Top-ranking reply

Owl-53

Level 10

113,589 points

Posted on Feb 7, 2026 4:58 AM

stevegoldfield wrote:

I know how to file bug reports; I have logged dozens of them, mostly never fixed including some bad ones. I wanted to see if anyone else is seeing the same thing first. I am also on an Intel 16-inch MacBook Pro running 26.2. Before logging anything new, I'm going to wait to see what other responses I get.

Using a M4 Apple Silicon computer running Tahoe 26.2

/usr/libexec/remoted is a legit Apple system daemon (used for Continuity / AirPlay / device handoff stuff.

When your MacBook Pro wakes, macOS tries to restart a bunch of background services in parallel.

Remoted is one of them, and it’s tightly tied to processes like AirPlay / Sidecar, Continuity (iPhone Mirroring, Handoff), External displays, Network state changes, (Wi-Fi reconnecting, VPNs), Bluetooth devices waking up,

On wake, one of its dependencies is briefly unavailable, so, remoted starts >> the watchdog pings

it does not respond fast enough >> watchdog logs a timeout >> macOS restarts the service silently >> everything works anyway

That is why it always happens after sleep

it doesn’t break anything, you only see it in logs

There are thousands of successful check-ins

View in context

32 replies