Hi,
Solution to test time can be risky if your schedule of the task starts at 08:29 or 08:31.
Try to test if time is greater than 08:25 and less than 08:35 so it should be the 08:30 theorical run that is executing this command.
You can also, if you use an event object to activate the job, create two separate event. One running from 08:00 every 10 minutes and ending at 08:25 (runtime options or test time and cancel with ended_ok status if time > 08:25. Second event object starts at 08:40 until 11:00.
Another option is to define time period for event activation from 08:00 to 08:25 and from 08:40 till 11:00. But check how it is reacting for the next run calculation if you need to be right on 08:40 for the run of the job. This setting is in the "Time and Date Conditions" section of the "Time Event" view of the Event Object in v12 or in the "Calendar" tab in versions < 12.
As usual there is multiple solutions to a problem and you just need to select the one you are the most comfortable with and that fit your requirements.
Alain
Original Message:
Sent: 08-08-2019 01:54 PM
From: Pete Wirfs
Subject: Skipping a particular cyclic run from Event
One option is to use a script like this;
:set &TimeToSkip# = "0830"
:if &TimeToSkip# = "&$PHYS_TIME_HHMM#"
: print "Not executing due to &TimeToSkip# skip rule."
: stop NOMSG
:endif
Another option is to instead of using an automated repeat rule, install a different run schedule for each instance that needs to run. This provides two benefits; (1) they show up on forecast reports and (2) you can customize your skip-run rules with calendar features too (e.g. skip at 0830 only on saturdays) The latter can be done with scripting too.
------------------------------
Pete (AE V11.2)
Original Message:
Sent: 08-08-2019 11:46 AM
From: Sunish Mittal
Subject: Skipping a particular cyclic run from Event
Hi,
We have a scenario / requirement
a job is running every 10 mins from 8AM to 11AM, application team wants that only 8:30AM run to skip rest shd run as per schedule. Means all runs starting from 8:00, 8:10, 8:20, ..... , 8:40, 8:50 shd run just skip 8:30 AM run
so is there a way in Automic to implement this scenario.
in other tools we can put an exception entry which will skip the run for that entry but same i dont see in Automic.
Any pointers or help is highly apperciated.