Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Creating a Queue Processor rule

Updated on April 5, 2022

Create a Queue Processor rule to queue your items. You can use a Queue Processor rule for immediate or delayed processing, for tasks such as sending emails to users or updating the database of user logins.

  1. In Dev Studio, click Create SysAdminQueue Processor.
  2. Add a label and a ruleset to your queue processor.
  3. Click Create and open.
  4. In the Associated with node type list, click a node type to associate with your queue processor.
  5. Determine the time when you want your queue processor to run by selecting one of the following options:
    • Immediate
    • Delayed
  6. In the Number of threads per node field, enter the number of threads that you want to process your items in a node.
  7. In the Class field, specify the class of an item that you want to queue.
    The class that you specify must contain the activity that you want your queue processor to resolve.
  8. In the Activity field, specify an activity that you want your queue processor to resolve.
  9. Optional: Modify any of the following fields:
    FieldField Description
    Max attemptsThe number of attempts that you want your queue processor to perform before the item is moved to the broken items queue. The default value is 3.
    Initial delay (in minutes)The amount of minutes for the processor to wait before retry to process an item. The default value is 1.
    Delay factorThe factor by which the initial delay value is multiplied to calculate the period of time between successive retry attempts. The default value is 2.
  10. Optional: In the Alerts configuration section, in the Long running queue processor threshold field, change the threshold for long running queue processor activities.
    An alert is saved to the log file when the activity’s execution time exceeds the threshold value. For more information, see PEGA0117 alert: Long-running queue processor activity.
  11. Click Save.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us