Maybe someone will catch something I'm missing, but I don't see anything wrong with the way this is set up, at least as it pertains to your lack of repeat. If anything, I think a lack of stopping would be a problem: your trigger is only "open," so nothing will happen when the door gets closed because no trigger will match and the ELSE section that I assume you intend to run in this case will not get a chance to do so (at least not until sunrise if you happen to open the door again).
To avoid that, I'd use this structure from the Rule Machine repeated notification thread I often refer people to:
Trigger Event: sensor(s) opened
Actions:
REPEAT every 0:01:00 (stopable)
IF (sensor closed OR time between sunrise and sunset) THEN
Stop Repeating Actions
ELSE
Notify devices "Door open and whatnot"
END-IF
END-REP
Still, this doesn't explain your original problem. If I had to guess, maybe you went to view the rule during the delay between the repeats (not a literal RM delay, so "delay" in the lay sense) and clicked "Done" when you were finished? That or "Update Rule" would cancel any scheduled jobs like the next execution of this repeat; the workaround is just to close the rule or navigate away instead (as long as you are not in the middle of editing an action and are just viewing your completed actions and triggers on the "main" rule page). In any case, something like the above would get you closer to what you want.
