Current time attribute inconsistent

So I was trying to nest a few rules while relying on current time attribute.

I have a f1 (monitor folder)
f1
--fs1
--fs2
--fs3

I have a rule that says
Current time is 9:07PM any day

do the following
set color label to red.

Which seems simple enough. The rule will run on any day at 9:07PM and color the items red otherwise it will not run. To test this i did the following:

but the issue is the following:
1 - if i change at 9:07 the set color to yellow wait until 9:08 then save the rule and run the rule manually or let it run automatically at 9:08 the contents all turn yellow at 9:08 or later randomly. Based on https://www.noodlesoft.com/manual/hazel ... reference/ this "So, if you set up a condition like “current time is after 10 p.m. on weekdays,” the condition matches only from 10 p.m. until midnight each weekday—Hazel does not consider 12:01 a.m. the following morning to be “after” 10 p.m." That means it should only run at 9:07 and at 9:08 it shouldn't run at all. But it does run.

So i'm trying to understand how that is possible and better how do I fix it?
not sure if something is broken in the time function.

Use "is after" and "is before". If you use "is", Hazel will match a period of time afterwards. That is because it cannot guarantee that rule will get evaluated right at 9:07. It has to fudge things to account for other things happening.

Mr_Noodle wrote:Use "is after" and "is before". If you use "is", Hazel will match a period of time afterwards. That is because it cannot guarantee that rule will get evaluated right at 9:07. It has to fudge things to account for other things happening.

By doing this (I don't want this rule to run more than just once in the time duration specified)
- desired time is 9:07

will this achieve this?
All
current time is before 9:08
current time is after 9:06

so now hazel will run at 9:07?

It should run once in that period, provided that there aren't other issues preventing it from getting to it within that time.

Mr_Noodle wrote:It should run once in that period, provided that there aren't other issues preventing it from getting to it within that time.

So I take it there isn't a FIFO queuing system in hazel if it doesn't run in that time frame.

Not sure how that's relevant, but like I said, there's a chance it won't get to it in that time. The details are esoteric but it's not as simple as that and it can't keep trying to execute a file as if it was at that time forever.