Troubleshooting and avoiding delays in SLA Agent processing

@MarijeSchillern

Thank you for the feedback. I have some questions. We are still working on version 8.6.6 - Regarding the items Agent Configuration Mismatch and Resource Allocation and Scaling.

Agent Configuration Mismatch:

  • Increase the agent interval to match or exceed the processing time.
  • Implement mutual exclusion settings to prevent overlapping executions.
  • Adjust the processing batch size (currently 500 records) based on system capacity.

Since the agent is native to the ServiceLevelEvents platform, which is in the Pega-ProCom ruleset, how could I promote this modification? Can I specialize this agent? Can you give me more details?

Resource Allocation and Scaling:

  • Consider dedicating specific nodes exclusively to SLA processing.
  • For on-premises deployments, consider scaling up (more resources per node) or out (more nodes).

Can I create specific nodes for SLA and indicate the agent to use these resources for processing? Given the same scenario, which is an OOTB rule, how can I apply this?