Noodlesoft Forums

Looking at some logs while trying to identify why my iMac is running super slow, I'm noticing this:

2012-03-12 19:36:53.791 (null)[0] Sending metrics to scheduler. Next scheduled run: 5828963-12-20 00:00:00 +0000

I don't think that my iMac will be running then, and I'll probably be dead.

Hazel 3.0.2 (build 775).

I think that I've fixed the performance issue I was having from Hazel (I had something scanning the iTunes music folder far too often; is there a way to force a particular folder be scanned at most once a day at a specific time?)-a

That message just means that, based on your rules and the current state of your files, Hazel doesn't need to wake up for any time-based reason. It will still wake up for file events but otherwise, it will lie dormant.

As for performance issues, check Activity Monitor and make sure it's actually Hazel causing the problem. You can use the "current time" attribute to schedule a rule but I think it would be more helpful to actually identify the culprit in this case.