Skip to main content

PEGA0117 alert: Long-running queue processor activity

Suggest edit Updated on May 14, 2020

A queue processor uses an activity rule to process an item. An activity can perform various operations, often accessing a database or external services in an inefficient way. Pega Platform™ generates the PEGA0117 alert when such an activity runs longer than a configured threshold value.

Pega Platform uses two kinds of queue processors: standard and dedicated. The threshold value for the PEGA0117 alert is configured differently for each type. For a standard queue processor, the threshold is configured in the Queue-For-Processing command’s parameters in an activity that queues items. For a dedicated queue processor, the threshold is configured in the queue processor’s Definition form.

Reason for the alert

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

Example message text

Long running queue processor activity{queue processor=TestQP, ruleset=DMSample_Branch_test, ruleset version=01-01-01, execution time (ms)=5481, exceeded threshold value (ms)=100} Producer operator{id=admin, name=admin} Producer activity{class name=DMOrg-DMSample-Work, activity name=QueueToTestQP, activity step=3, ruleset=DMSample_Branch_test, ruleset version=01-01-01, circumstance=0} Consumer activity{class name=@baseclass, activity name=Accelerate, ruleset=Pega-ProCom, ruleset version=08-01-01, circumstance=}

Dynamic system settings for this alert

The PEGA0117 alert is enabled by default. To disable the alert, set the following dynamic system settings:

  • Owning ruleset: Pega-Engine
  • Setting purpose: alerts/queueprocessor/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 which operation performs the longest. You can perform this action by using the Performance Analyzer tool or Tracer tool. Slow operation might result from inefficient data retrieval from a database (too much data or an inefficient query) or accessing slow services. Check related alerts for a sign of slow data access or integrated services.
  • Adjust alert thresholds
    An activity can perform various tasks of different length. For best results, adjust the threshold value for activity execution time for each queue processor. Defining a threshold value depends on an activity’s purpose. Activities that perform in-memory data page operations are usually fast and require different threshold values than activities that send emails, which depend on network latency and the email server’s responsiveness. As a result, the optimal threshold value for an activity might range from milliseconds to seconds, and only the author of the activity can define the correct value. For a standard queue processor, the threshold value is defined in the activity that submits an item for processing. For a dedicated queue processor, the threshold value is specified in the queue processor’s definition.
  • Use a dedicated queue processor
    A standard processor might be overwhelmed if all applications in the system use it. In such a case, when more processing power is required, consider using a dedicated queue processor.
Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us