Working with Events › Active Events › Event Bypass and Unbypass › Skipped Bypass Requests

Skipped Bypass Requests

Event bypass requests can be skipped if the scheduled time of an Event execution changes after the bypass request is made. For example, a bypass request can be skipped if an Event is manually triggered to replace the Event's next scheduled execution or if the definition of a special day used in an Event's scheduling criteria changes. You can list skipped (invalid) bypass requests.

Example: Skipped Bypass Requests

Consider the following scenario:

• A special day named festivus is defined in a calendar for the following days: June 10, August 10, and September 10.
• An Event is scheduled is to run on the days defined by the festivus special day. In the Event definition, the scheduling criteria references the special day (for example, SCHEDULE 9AM FESTIVUS).
• A user decides to bypass the Event execution scheduled on August 10 and issues a bypass request.
• Another user updates the definition of the festivus special day, replacing August 10 with August 11.

Because the Event no longer triggers on August 10, the bypass request for August 10 is now invalid and will be skipped. Instead of August 10, the Event triggers on August 11.

More information:

List the Skipped Bypass Requests of an Event