Why are there zero events for these configurations?
The only schedule I can create is one that either starts within 1 week or runs every day. If I want to further define a schedule, it does not include any run days.
I'm not sure I follow. If you want to pick "random" days of the week, then you choose weekly. The next run of it would be on the nearest selected day and time.
What schedule are you trying to create?
At first I wanted to create what is shown in the second screenshot. A schedule that starts on Monday the 24th and runs every Monday.
It happens as soon as you touch the AM/PM component of the time picker (at least it does for me). If you edit your rule and toggle 8:00 AM to 8:00 PM I bet you will see test cases successfully shown. Also it only occurs if the value for every ___ week is set to 1. If you increase the number test cases will appear but obviously the schedule would be different from what you desire.
The working solution I found was to choose Repeats Daily and then set the interval to Every 7 day. Then just ensure that you select the appropriate Start on date.
An additional related oddity is that the test cases shown appear to interpret the time input using the users local browser regional time settings and convert the time value to the time zone selected on the staring event form. For example, When I choose 8:00 PM as the time and leave the default time zone as (UTC-08:000) Pacific Time (US & Canada), my test cases show 11:00:00 PM. My local browser region is (UTC-05:00) Eastern Time (US & Canada). This may be by design but it doesn't make things super clear and could likely benefit from some on screen verbiage.
I see what you mean. It seems to be a bug with figuring out when the next run is. If the first run is more than a week ahead, both testing it and validation fail. In your example, tomorrow is Wed, but it does not fit the schedule.
We'll look into it. Reference ID # 527159
It is also not clear if "start on" means that it will trigger on the day selected even if it does not match your schedule, or if it is just the day where the rule becomes activated. It seems like it should be the latter and say "activate rule starting on" as an option, otherwise the rule is active by default
It's meant to be using all criteria together to figure out when the next run is. So with the 3rd screenshot in your original post, it would be Mon, 6/24 at 8AM. Then again on Wed, 6/26 at 8AM and so on.
Whether the rule is active or not is controlled by the "enabled" toggle on the first step. If the rule is active, it will run on the first matching date. If the rule is not active, the criteria one this step is irrelevant because the next run time will not be calculated.
Well things get strange if I pick Sunday as the Start On date and to run every Monday as my rule. It obviously shouldn't start on Sunday, so the Start On is truly more like an activate on date.
Sure, it's a "on or after". Or, I guess, a "not before this date" for your Sunday start for a schedule that is expected to run on Mondays.