Stop Task Execution
Sometimes a task encounters a problem, such as when an on-premises system is not returning information, and the task becomes unresponsive. To address this issue, you can stop the task execution, which halts any pending processes. Only users with either the Super Admin role or the Configuration Admin role in SAS Customer Intelligence 360 have sufficient access to stop task execution.
Bulk Email and Bulk Push Notification Tasks
To stop the execution of bulk email or bulk push notification tasks, first determine whether the task needs to be stopped.
- Access permissions in one of these
ways:
- If the task has an Orchestration tab, click it. Navigate to the Execution page.
- For all other tasks, click
and click Stop Task
Execution.
- Click
to refresh the task. - Note the value of the Most
recent update time. This value reflects when the system most
recently recorded an update for this task execution.
Note: This value is updated only when the task is refreshed.
- If the value has not changed in some
time, click Stop Task Execution to check the progress
of the task.
Review the data that is available and determine whether you want to stop the task. The data includes these execution details:
- Total Recipients shows the number of recipients in the segment or target audience.
- Recipients Processed shows the number of recipients who have been processed so far.
- Recipients Completed shows the number of recipients who were successfully sent an email or a push notification.
- Recipients Failed shows the number of recipients who could not be sent an email push notification.
- Recipients Skipped shows the number of recipients who are skipped by the system. The system skips recipients for various reasons. For example, if the recipient's impression limit was achieved or the recipient did not meet the trigger criteria. Another example for push notification tasks is that the device might be unreachable. For email tasks, examples include that the recipient might have opted out or previous email messages to them have hard bounced.
- Stopping the task execution of an email task halts delivery of any unprocessed emails.
- Stopping the task execution of a bulk push notification task halts delivery of any unprocessed push notifications.
If you decide to stop the task, click Yes. To exit without stopping the task, click No or close the window.
CAUTION
Re-running the task sends emails to all of the recipients in the target audience, even if the email was sent to the recipients previously. As a result, running a task that was previously stopped can result in duplicate emails being sent to recipients.
CAUTION
Re-running the task sends push notifications to all of the recipients in the target audience, even if the push notification was sent to the recipients previously. As a result, running a task that was previously stopped can result in duplicate push notifications being sent to recipients.
Direct Tasks
In some circumstances, such as when the direct marketing agent is down or there are errors in a custom stored process, a direct marketing task might remain in the Running status for an indefinite amount of time. However, it is possible that the task appears to be unresponsive because the execution is taking a long time, even though the on-premises agent is running.
To address this issue, click the Activate the Non-Responsive Item button to move the status of the item from Running to Active with an error. When the button is clicked, any jobs that are associated with the direct marketing task and that are currently running on the on-premises system run to completion. Any pending jobs for the task are prevented from running. The direct marketing task stops and returns to the Active status with an error message that is cleared when the task is republished or run again.
For more information, seeSchedule and Execute Your Direct Marketing Task.