| Print Open PDF Version of Online Help

#### Workflow Wait Monitor From the Workflow Wait Monitor, you can view the details of the following: Pending instances of Wait actions and details of those workflow actions. Instances of scheduled events (that is, workflow rules with the Scheduled Event trigger event) that are pending or are currently executing. For example, if an instance of a workflow Wait action or an instance of a scheduled event is pending for longer than you expect, then you can use the Workflow Wait Monitor to investigate the instance and look at the configuration of the workflow rule, scheduled event, or workflow action. If necessary, you can delete the instance. NOTE: When you delete a pending instance of a Wait action, none of the remaining actions on the workflow rule are performed. When you delete a pending instance of a scheduled event, the instance of the event is cancelled, the status of the scheduled event is set to Terminated, and the scheduled event is deactivated. No further instances are generated for the remaining occurrences of the scheduled event. ### Pending Instances of Wait Actions To understand how pending instances of Wait actions are processed on a workflow rule, consider the following example. You might configure a workflow rule with the following intended sequence of actions: A Wait action with a duration of 24 hours A Send Email action A Wait action with a duration of 48 hours A Send Email action A Create Task action If the actions are correctly configured, then the first Wait action in the sequence, action 1, remains in the Pending state for at least 24 hours. After the wait period ends, the Send Email action (action 2) is performed. The second Wait action (action 3 on the workflow rule) is next in the sequence. It remains in the Pending state for at least 48 hours. After the wait period ends, the Send Email action (action 4) and the Create Task action (action 5) are performed. NOTE: The wait period specifies the minimum amount of time that must pass before Oracle CRM On Demand starts to execute the other actions on the workflow rule. The actual amount of time that passes before the other actions are executed might be longer, depending on the load on the Oracle CRM On Demand database and the Oracle CRM On Demand server, and also on the number of Wait actions that are pending when the wait period ends. However, if the wait period on action 3 was incorrectly specified as 48 days rather than 48 hours, then the action remains in the Pending state until 48 days have passed. You can see the action in the Workflow Wait Monitor, and you can view the action details to see whether the wait period is incorrectly specified. You can then delete the Wait action instance. When you delete the Wait action instance, the workflow rule instance is terminated, and the remaining actions on the rule instance are not performed. In the previous example, the following occurs: If you delete action 1 while it is pending, then actions 2, 3, 4, and 5 are not performed. If you delete action 3 while it is pending, then actions 4 and 5 are not performed. NOTE: Wait actions are the only type of workflow actions that are held in the Pending state. ### Pending Instances of Scheduled Events A pending instance of a scheduled event remains in the Queued state until the date and time when the instance is scheduled to be executed (the resume date). The resume date is the earliest possible time that the instance will be executed. Depending on the load on the Oracle CRM On Demand database and on the Oracle CRM On Demand server at that time, and on the number of Wait action instances and scheduled event instances that are pending, the instance might not be executed immediately. After the instance starts to execute, the status of the instance changes to Running and the Actual Start Date field is populated. You might need to refresh your browser page to see the updated fields. The instance continues to appear in the Workflow Wait Monitor while it is executing. If necessary, you can delete an instance of a scheduled event while it is executing. If you do so, then the instance is removed from the Workflow Wait Monitor. In addition, the status of the scheduled event is set to Terminated, the scheduled event is deactivated, and no further instances are generated for the remaining occurrences of the scheduled event. The instance continues to execute until the next time that Oracle CRM On Demand checks to determine if the scheduled event is still active. This check is performed at five-minute intervals during the time that an instance is executing. When Oracle CRM On Demand determines that the scheduled event has been deactivated, the instance that was executing terminates, and any workflow action that has not already been performed for the instance is not performed. You can also delete an instance of a scheduled event while it is pending (that is, while the status is set to Queued), as described in Deleting Pending Instances from the Workflow Wait Monitor. #### Related Topics For information about scheduled events, see the following topics: About Scheduled Events Creating Scheduled Events For information about using the Workflow Wait Monitor, see the following topics: Viewing Pending Instances in the Workflow Wait Monitor Deleting Pending Instances from the Workflow Wait Monitor Workflow Pending Instance Fields

Published August 2022 | Copyright © 2005, 2022, Oracle and/or its affiliates. Legal Notices.