Working with Events › Active Events › Event Hold and Release

Event Hold and Release

You may need to postpone an Event at times. To postpone an Event, you must instruct the server to hold it. The Event remains in the on hold state until you release it. When you want to release the Event, you instruct the server to release it.

The server marks an Event as overdue in the following cases:

• For scheduled Events—if an Event's scheduled time occurs while the Event is being held
• For monitor Events—if an Event's condition is met (for example, a file is created for a File Trigger Event) while the Event is being held

When you release an overdue Event from hold, the server immediately triggers the Event once, regardless of the number of missed executions. The server uses the time and date of the last missed execution to select the jobs and resolve scheduled variables.

Note: If you want to prevent future executions of an Event from triggering, suspend the Event instead. When you resume the Event, the missed executions are skipped. If an Event is both suspended and held at its scheduled execution time, the server ignores the on hold state and considers the Event suspended.

Example: Hold and Release an Event

Consider the following scenario:

• At 3 p.m., you are asked to postpone an Event named ACCNT.PAYROLL, which is usually processed at 4 p.m. daily.
• You hold the Event named ACCNT.PAYROLL.
• At 4 p.m., the server does not process ACCNT.PAYROLL because it is on hold.
• At 5 p.m., you are instructed to let ACCNT.PAYROLL process.
• You release the Event named ACCNT.PAYROLL.

By default, the Event then processes because the server knows the Event missed its scheduled execution at 4 p.m.

More information:

Hold an Event

Release a Held Event