How to detect when a generated stream was overwritten but never sent (PEGA0031 alert)

This alert can identify processes, for example, an activity, where two streams are created, but only the last stream can be used. An overly simplified example is an activity where two show-property methods are executed one after the other. This alert is triggered when the output of the first method is overwritten by the output of the second.

Note: If the Trace List setting is not enabled for alerts generation, enable it for troubleshooting with this alert. You may wish to set this entry higher than the default to get more depth of information. The Trace List option can be resource-intensive, and you may wish to reset it to the default value of 5 after troubleshooting.

Alert log message

A PEGA0031 alert is generated when a starting activity or stream has generated multiple response streams during a single interaction. If multiple streams are generated, then only the last one is sent to the workstation browser (client).

System resources were used to generate the previous screens with no benefit to the interaction. Here is an example of the message:

Overwritten HTML stream

This alert can be configured to optionally capture overwritten generated streams with a dynamic system setting. See PDN article Understanding the PEGA0031 - Generated stream overwritten and not sent to client.

Remediation

When this alert is triggered, examine the alert to determine the activity or process that triggered the alert. Examine the last step, initial activity, and the trace list in the alert to determine what streams are being generated during the interaction. Remove any earlier stream generations that are subsequently overwritten.

	alert log, prconfig.xml file, stream processing
	Understanding alerts

SysAdmin category