Hi, no you don't need to use the Repeating settings in your case. They're for running 'inside' the Recurrence cycle, for example if you want 'hourly', you have to Recur every 1 day (the max frequency MS* allow for Recur) and Repeat every hour for 23 hours. You shouldn't ever use Repeat > Indefinitely unless your Recur is set to [0] (it's designed for trigger events that only happen once in a session, e.g. On Logon). If you have a Recurrence and also Repeats > Indefinitely you can (using the above 'hourly' example) get clashes when the second Recurrence (next day) and the 24th Repeat coincide...and so on.
Yes, setting the Weekly > Recur Every [1] Week on [click day required] is enough, and the fact you're getting that error shows it's working (triggering) but is then self-cancelling (without calling SE) because of a 'constraint' in the Task (nothing to do with the timing, usually)
We have a KB article on the concept, but we can't tell you which constraint is causing it to self-cancel (because Windows 'usefully' doesn't say)
( * BTW, in case you didn't realise, there is no scheduler in SE/Pro itself - what you see in SB is a drill-down to the Windows Task Scheduler service)
Yes, setting the Weekly > Recur Every [1] Week on [click day required] is enough, and the fact you're getting that error shows it's working (triggering) but is then self-cancelling (without calling SE) because of a 'constraint' in the Task (nothing to do with the timing, usually)
We have a KB article on the concept, but we can't tell you which constraint is causing it to self-cancel (because Windows 'usefully' doesn't say)
( * BTW, in case you didn't realise, there is no scheduler in SE/Pro itself - what you see in SB is a drill-down to the Windows Task Scheduler service)