Hi Alonso,
in order to run a job every minute you choose the "repeat" set to 1 minute.
In the next line you can then filter out the unwanted period between 22:30 and 22:40.
The problem with the "range of day" here is that you can't specify a negated period (not 22:30 - 22:40), and if you specify something like "22:40 - 22:30" it will select everything because there aren't times in that range _on a single day_.
(It will select all times t with 00:00 <= t <= 22:40 or 22:30 <= t <= 24:00).
You'll have to build that yourself for now. And this can be done with the Interval editor.
In the Interval editor you create an Interval of type "List" and select 'T2230 - T2240' with an INVERSE selection. (Note the missing colons in the time specification here).
Let me assume you call this interval RANGE2230_2240.
Now you can add the second line to the job schedule. You use the Calendar Filter here and select your RANGE2230_2240. Don't forget to change the "With Select On" field to "Day".
(It would work with "Month", but you'll be rewarded with a performance penalty. The engine processes it as if you had entered a selection and would have to collect all the minutes of the month before it would be able to apply the filter. That's roundabout 30 times slower than collecting the minutes of a single day)
Oh and set the Calendar to "INACTIVE". You don't need to know in advance when it will run because it will run every minute.
No need to store those start times in the database, it's a loss of computing power and disk space for nothing.
I've added some screen shots. I hope that helps you to understand the written text.
For the sake of the example, I selected different times and set the Calendar to ACTIVE. This way you can see it works as required (the times between 11:40 and 11:50 are missing).
Best regards,
Ronald