So I am not sure if this is an RM bug and the trigger should work without specifying a time, or if it's a UI bug and my trigger should not have been accepted without specifying a time.
No, the asterisk means that this field ("At this time") is required (there's an aversion in RM to making the fields literally required, i.e., un-submit-able, but I don't know the exact reason besides making it more difficult to remove things you don't really need later). It has to happen at some time on that date, so filling in midnight if that's what you want is certainly fine.
Right. I admit I didn't see or pay attention to the asterisk - my bad.
I guess I was expecting the UI to tell me if I forgot something critical, or pre-fill the fields with something valid (like an "and stays" trigger, which sets zeroes by default)
I thought about this some more and decided to do things a bit differently. I need to ensure the rule runs at least once within a given period (and as soon as possible within that period), so having a trigger at a specific time and date seemed... brittle.
(I could have used the rule's private boolean to ensure it runs only once)
Perhaps I'm overdoing it and there is a simpler way to achieve the same result?
