How Do I Keep Track of Scheduled Processes That Were Already Submitted?

To make sure that the scheduled processes that your users submit run smoothly, constantly keep track of the submissions.

Here are some key things that you can do in the Scheduled Processes work area to track and get information about the submitted processes:

Use the saved searches to see the processes that were submitted within a specific time frame, for example in the last hour or 24 hours.
Select specific processes in the search results to get details about the process:
- Status Details tab: More information about the current status of the scheduled process, for example to see incompatibilities for a blocked process.
- Process Details tab:
  - A log, if available, to see the stages the process has gone through, information or error messages, and other information about how the process ran or is running.
  - Parameter values that users submitted the process with. For example, parameters often determine the amount of data to work on, so parameter values might explain why a process is running for a long time.
Use the Hierarchy view when looking at a problematic job to help you determine why a parent is stuck. The default Flat List view doesn't show if the job has sub requests.

Keep the following best practices in mind as you monitor scheduled processes.

Track the Amount of Traffic in the Queue

In the Scheduled Processes work area, regularly check how many processes are currently running or waiting to run. Pay attention to processes with these statuses.

Ready: That might mean that the maximum number of processes running at the same time was already reached. So new submissions are now in the queue.
Wait: That might also mean that the limit has been reached, but usually it means that the process is scheduled to run in the future.
Blocked: Check the Status Details tab to see what incompatibility is preventing the process from running, and take any appropriate action.

Change the Priority of Processes in the Queue

When there are many processes in the queue, consider changing their priority, especially processes with the Wait status. This way you make sure that the more important processes run first.

Monitor Processes Running for a Long Time

Keep an eye on processes that have had Running status for days, or even weeks. You might need to investigate if there's a business reason holding up the process, or consider if you might need to cancel those and resubmit.

You can check for processes that have been running for a long time, using the SQL queries given in Sample SQL Queries for Monitoring Enterprise Scheduled Services (ESS), Doc ID 2820161.1.

If you have many processes to cancel, you might be able to cancel some or all of them in bulk. But before you do that, select each one and see its details to make sure you really want to cancel it.

Note: Use the Force Cancel option to cancel processes that have been canceling for over 30 minutes but isn't done yet.

Cancel and Reschedule Processes for Inactivated Users

If a user is inactive, for example because the user left the company, the processes they submitted on a recurring schedule won't run.

For security reasons, it's best that you cancel that submission and schedule a new one if still needed. The same situation applies to users who are locked or failed to authenticate.