Working with Events › Events › Suspend and Resume Times

Suspend and Resume Times

Suspending an Event prevents the Event from triggering until you resume it.

Using Event-control criteria, you can schedule the suspending and resuming of Events. You might schedule an Event to occur within a range of time, resume an Event that was suspended manually, or suspend an Event at some time in the future.

Suspending a scheduled Event for some time in the future is useful if you are running an Application multiple times each day. Suspending a monitor Event for some time in the future is useful if you want to monitor for a trigger condition during a specific window of time.

Note: When you specify a suspend time, specify a time before the Event's scheduled or expected time; otherwise, the server may not suspend the Event in time. We recommend you use a suspend time of at least one minute before the Event's scheduled or expected time. For example, if your Event is scheduled for 8:00, to suspend it, specify a time of 7:59 or earlier. Similarly, to resume an Event, specify a resume time of at least one minute before you want the Event to resume.

When specifying suspend and resume times, consider the following:

• If you specify a day and month in your Event-control criteria, you must include the year, for example, APR 1 2006.
• If you want to suspend an Event on a particular date, specify an absolute date (for example, 9:01 March 1, 2006) instead of a relative date (for example, 9:01 TOMORROW).
• You cannot specify some scheduling terms in suspend and resume times, such as the following:
  • Starting time/date and ending time/date (such as HOURLY STARTING 2PM TODAY)
  • Every n units (such as, EVERY 5 MINUTES)
• When an Event is manually suspended, its suspend count increments by one. If you specify a scheduled resume using Event-control criteria, the suspend count decreases to zero regardless of its current suspend count.

More information:

Specify Suspend and Resume Times