Skip to main content

PEGA0029 alert: HTML stream size exceeds limit

Suggest edit Updated on May 18, 2022

Pega Platform™ generates the PEGA0029 alert when the size in bytes of an HTML stream that a browser processes exceeds a threshold value. This alert identifies the keys to the top-level stream rule that crossed the threshold. The alert analyzes the size of raw data before compression for any single HTTP request.

If the target of the HTTP request contains multiple sections, Pega Platform generates this alert when the whole HTTP stream exceeds the threshold. The alert contains the last section which was able to load as reference to help investigate the issue.

Reasons for the alert

Very large HTML streams add to overall network traffic and usually require the browser to work longer to render the display, which slows system performance in the perception of the users.

The alert can occur when a page contains too much content or large lists.

Example message text

Stream exceeded client response byte threshold (pxObjClass=Rule-Obj-HTML;pyStreamName=Web-Login;).

The other fields in the alert log message identify the pzInsKeyor the rule class of the stream as well as the keys of the stream.

Default prconfig.xml settings

In the alerts section of the prconfig.xml file, you can update the following default values for this alert:

<env name="alerts/clientbytesreturned/enabled" value="true" />

The enabled setting switches the alert on (true) or off (false). The default value is true.

<env name="alerts/clientbytesreturned/threshold" value="204800" />

The threshold setting is a positive integer that identifies the size in bytes. The default threshold is 1,000,000 bytes (more than 976 KB).

<env name="alerts/clientbytesreturned/ignoredevusers" value="true" />

The ignoredevusers setting switches on or off the alert for streams that originate in a developer portal (authenticated users who can check out rules). The default is true, which suppresses the alert. To activate the alert, set the value to false.

    Recommended next steps

    If a page contains too much content, consider moving that data to separate pages. Also, try moving any non-dynamic elements such as CSS style sheets and JavaScript script code into static content by using a text file rule (Rule-File-Text rule type) to reduce browser traffic and take advantage of client-side caching mechanisms.

    If a page contains large lists, implement a paging mechanism for those lists.

    Did you find this content helpful? YesNo

    33% 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