SendPMFINRAReportData agent timing out after schedule run, and manual rerun returns empty fields

General
,
1

Hello Pega Community,

In our project, we have an agent named SendPMFINRAReportData that runs on weekdays at 6:00 AM EST.

Initially, the agent timeout was set to 30 minutes. It generated the report successfully when the scheduled run completed, but after that, the agent started timing out every day. To generate the report, we had to run the agent manually.

We then increased the timeout from 30 minutes to 120 minutes. This worked for some time, but now the agent is timing out again.

Also, when we manually rerun the activity to generate the report, some fields return empty values.

Could you please suggest what actions we should take to resolve this issue?

Thank you.

2

Hello @JaiganeshK17634894 Welcome to the community

Let’s start with the basics. Which version of Pega are you using now?

From the symptoms, this does not look like just a timeout issue and apparently, increasing the timeout only provided temporary relief, which indicates underlying performance degradation.

A few key areas to focus on:

  • Agent execution context: Ensure this (likely Advanced Agent) is running on a dedicated node with proper node classification.
  • Data volume & query performance: Check if the dataset has grown over time. Use DB Tracer and validate indexes on filter columns to identify slow queries.
  • Integration latency: If external systems are involved, review response times, timeouts, and retry behavior.
  • Empty fields on rerun: This points to partial processing or step failures. Trace the activity to verify clipboard population and error handling.
  • Logs & PDC: Look for patterns like long-running queries (PEGA0005) or agent-related alerts (PEGA0020).

Also, if this report involves large-volume data processing, consider redesigning the solution:

  • Use Data Flows for backend data preparation (parallel, scalable processing)
  • Then trigger report generation via Job Scheduler/Agent

This hybrid approach helps avoid long-running agent executions and improves reliability.

Overall, the issue is likely due to increasing data volume, query/integration slowness, or execution context issues, rather than just timeout configuration.

If you can investigate on the above mentioned areas, then most likely you should be able to find out the root cause.

Hope this helps

Regards

JC