ls: fts_read: Operation timed out

Never attempt to directly access any ".Trash" folder. The "Trash" is a Finder object. It exists only the form of the Trash icon in the Dock.

Any folders you might find in the Terminal that appear to be related are, at best, "implementation details". Any attempt to access them directly is unsupported and risks catastrophic data loss. So don't do that.

Instead, start by providing more information about this:

I'm trying to investigate a problem with (Noodlesoft's) Hazel throwing an error on (Microsoft's) OneDrive's trash, which I thought was empty.

Generally speaking, until you notice some problem in your normal usage of the computer, then there is no problem.

If you start digging into Console message or using Terminal, looking for problems, you are absolutely guaranteed to find them. There is literally an endless supply of scary sounding messages and mysterious behaviours. And I just don't mean "many", I mean it literally endless, hundreds of messages a second, every second until the end of time. Terminal has hundreds of command line tools, some have never been test by Apple in decades.

These cloud services are becoming a major source of problems. Apple's security requirements have forced them all to adopt Apple's own APIs. Those APIs aren't easy to use and may be unreliable because they are so new. You have at least two installed and running - Box and OneDrive, not to mention iCloud. Are they configured so that they don't interfere with each other? Can they be configured so that they don't interfere with each other? No one can answer those questions.

Probably the one thing you can do is see if you can access your data on these cloud services using some kind of web interface. The idea is to get find out what the "truth" about your data is. We often recommend people do this with iCloud too. Check the files that you can see as well as the space available. Make sure everything is as it should be.

That's not what I meant. You're in a rabbit hole. How did you get there? Something must have inspired you to go looking in the trash using the command line. So what actually happened?

It's difficult to follow a conversation second hand. But the developer is giving you good feedback. What were your answers? Did you actually have any files in that trash?

I don't know anything about that app. I certainly wouldn't dispute the claim that cloud services are super flaky. OneDrive is using Apple's new File Provider API. Any new Apple API is also going to qualify as super flaky.

But more importantly, the trash is still a Finder artifact. It belongs only to the Finder. Regardless of what problem with the Finder/Trash you are having, poking around in Terminal will only make it worse. Apple's cloud services API may have its own Trash interface. So what does Hazel have to do with any of this? OneDrive and Trash is a matter for only OneDrive, Finder, and various background Apple processes. Hazel should not be involved in any way. That would be bad. Real bad.