LinkedIn
Copied!

PEGA0118 alert: Long-running job scheduler activity

Pega Platform™ generates the PEGA0118 alert when an activity in a job scheduler runs for a longer time than the configured threshold value.

Job schedulers run in the background and execute a configured activity. Such processing is very specific to the business domain of a Pega Platform application. An activity can perform various operations, often accessing external data sources or services in an inefficient way.

A threshold value for the PEGA0118 alert is configured along with a job scheduler’s configuration. This value is part of the Job Scheduler rule and is configured in the job scheduler’s Definition form.

Reason for the event

An activity’s execution time depends on what the activity is using when it is running. Consider the following possible reasons for the delays:

Example message text

Long running job scheduler activity{job scheduler=Pega0118AlwaysAlerting, ruleset=AsyncPro, ruleset version=01-01-01, execution context=System-Runtime-Context, execution time (ms)=1524, threshold value (ms)=500} Activity{class name=@baseclass, activity name=SimpleLog, ruleset=AsyncPro, ruleset version=01-01-01, circumstance=}

Dynamic system settings for this alert

The PEGA0118 alert is enabled by default. To disable this alert, use the following dynamic system settings:

  • Owning ruleset: Pega-Engine
  • Setting purpose: alerts/jobscheduler/longrunning/activity/enabled
  • Value: false

Recommended next steps

To resolve the issue, consider the following actions:

  • Optimize activities
    Check the activity's performance to determine the longest operation that it performs. You can perform this check by using the Performance Analyzer tool or Tracer tool. Slow operation of an activity might result from inefficient data retrieval from a database (too much data or an inefficient query) or accessing slow services. Check related alerts for signs of slow data access or integrated services.
  • Adjust alert thresholds
    An activity can perform various tasks of different lengths. The threshold value is specified along with the job scheduler definition. For best results, adjust the threshold value for activity execution time for each job scheduler. For more information, see Managing job schedulers.

If the activity is already tuned and the processing time is still long, consider the following solutions:

  • Add more nodes for processing scheduled items. Using additional nodes might help if a job scheduler operates on data that is processed by several job schedulers.
  • If possible, divide the activity into smaller activities that are scheduled separately.
  • If a job scheduler is processing data in batches, consider using background processing, for example, queue processors for chunks of data.
Suggest Edit

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.