Remoted throwing errors every day

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

stevegoldfield wrote:

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: remoted < Remote Service Discovery daemon>

Well this is a good question.

I am seeing the same thing on an Intel 16" MBP running 26.2 thinking it started with 26.2 and hoping 26.3 may be some relief.

I have not figured out a course of action to resolve the issue

Send in the problem report each and every time it appears will help Apple prioritize and take action.

To be proactive you can file a bug report / submit your feedback here:

https://www.apple.com/feedback/macos

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.

"Why is removed throwing errors every day? "

I'll ask the mods to correct the title misspelling to help your efforts stevegoldfield ...

re: < remoted >

stevegoldfield wrote:

There is no misspelling in the title.

yes they fixed it— your original title read ""Why is removed throwing errors every day? ""

If it read correctly I would not of reported it....you got the word correct in the context of your original post as my reference point to commiserate with you...

Hey Stevegoldfield!

Thanks for all the info! Although I think more info could help with your inquiry:

I know of this process, however could you please explain in detail when exactly this prompt appears?

In what app or feature this error appears?

If this occurs after doing any particular task, or after say a restart?

And finally hat you have to do to temporarily correct this action?

Thanks!

I'm also seeing this error pop up multiple times a day. Started within the past week or two. I'm also on an Intel 16-inch MacBook Pro on Tahoe 26.2. Just filed a bug report as well.