In some situations, you may want to stop or pause an event manually (e.g., to add to or change it, to allow certain Users to respond, to check for false alarms, etc.). After you have launched a Scenario, you can stop, suspend (i.e., pause), and resume it from the Scenario Status Summary Report. This report appears automatically after you launch a Scenario via the web user interface.
When a Scenario is suspended, no new work is sent to Device Engines for processing. However, notifications that have already been sent to a Device Engine will be processed. All message responses that occur after a Scenario is suspended will still be valid and executed.
Ten Users are notified via a single Scenario, and then the Scenario is immediately suspended. If an email notification was submitted to a User prior to the Scenario being suspended, and the User response is ACK or some other job control, the requested activity will still be executed.
When a Scenario is resumed, processing will continue from the point at which it was initially suspended. However, the current date and time will be used for processing. Note that if a suspended Scenario is terminated by another application or mechanism (e.g., via a Management System), resuming the Scenario will not result in any further activity.
A Scenario targets Group1 (available 9am – 4pm on business days) to be notified at 3pm, and then the Scenario is immediately suspended. The Scenario is resumed at 8:30pm. No additional notification will occur until the next business day at 9am (if the Scenario is still active).