1. Best Practices for Scheduled Processes
  2. Why Are Scheduled Processes Running Slow or Not Running at All?

Why Are Scheduled Processes Running Slow or Not Running at All?

There's a limit to the number of scheduled processes that can run at the same time. That number depends on the setup for your cloud service. If you need more information, contact your help desk.

To manage the capacity and streamline batch processing, identify the scheduled processes that your users need to run, and plan out when and how often to run them.

You can find information about many of the predefined processes:

Here are some things to do and keep in mind when you design your plan. Also, see the rest of this chapter for more details about planning. For more best practices information, see Additional Optimization Opportunities for Scheduled Processes.

Avoid Having Too Many Processes Run at the Same Time

For processes that take more than a minute to finish, schedule them to run at a time when there are fewer scheduled submissions in the queue, that is, during nonpeak hours.

If you're submitting processes through web service from a third-party tool, review the time gap between each invocation. The gap between invocations means the time taken before submitting a new request. These processes are submitted using a SOAP client or Oracle Integration Cloud (OIC). In the Scheduled Processes work area, you're limited to submitting processes one by one, while from SOAP UI, you can submit multiple processes in a short period of time.

Related Topics

Set Appropriate Frequency for Recurring Schedules

When you plan for a process to run on a recurring schedule, set an appropriate frequency, ideally with the longest intervals possible.

If running the process once a day would meet your business needs, don't plan to run it more frequently than that. If anyone attempts to run a process with an inappropriate frequency, such as every one or two seconds, they can adversely affect performance and prevent any process from running.

For example, if a process usually takes 5 minutes, don’t schedule it every 4 minutes. In any environment, it’s not possible to make sure that a process will complete in a particular time. So, you can test to determine the average time certain processes take to complete, and then schedule accordingly, leaving some additional time between the runs.

Consider the Order to Run Processes In

Keep in mind which processes need to be run in a specific order.

If there's a process to calculate taxes that are deducted from a payroll, and another process to generate payroll, you should plan to schedule the tax process to run before the payroll process.

Prevent Incompatible or Blocked Processes

Incompatible processes can’t run at the same time. If a scheduled process has a Blocked status that means another process that’s currently running is incompatible with the process and preventing the process from starting.

A process can be self-incompatible, which means it can’t start if another submission for the same process is currently running.

Although blocked or incompatible processes can be resolved, consider incompatibilities when you plan. For example, if you know that certain employees need to run a process that is incompatible with a process that their manager runs, design your plan accordingly so that the employees and managers run their respective processes at different times.

Related Topics

Never Schedule Processes that Raise Processing Events

Processes that raise processing events must never run on recurring schedule. You must run these processes only as needed.

Here are few examples of processes that raise processing events:
  • Send Pending LDAP Requests
  • Auto-Provision Roles for All Users
  • Send Personal Data for Multiple Users to LDAP