To prevent an execution of an Event from triggering, you can bypass the Event execution. You can bypass the next scheduled execution or future scheduled executions of an Event. You can only bypass scheduled and manual Events.
For example, suppose that an Event triggers at 7 p.m. daily. At 3 p.m., you decide that the Event should not run that night. To prevent the Event from running the one time, you bypass the next scheduled execution of the Event.
When you list the Events scheduled within a specific period, Event executions to be bypassed are displayed in a different color. You can view the details of a bypassed Event execution to find out which user requested the bypass and when the request was made.
You can unbypass a bypassed Event execution before the server bypasses the Event execution. For example, if an Event execution is bypassed by mistake, you can undo the action by unbypassing the Event execution. At the Event execution's scheduled time, the server triggers the Event as usual.
Important! If an Event is modified, the server reschedules the Event and all existing bypass requests against that Event are lost.
Example: Lost Bypass Requests
Consider the following scenario:
Because the Event was modified, the server reschedules the Event for Monday, Tuesday, and Thursday. The bypass request is lost and must be issued again.
|
Copyright © 2014 CA.
All rights reserved.
|
|