Out‑of‑Memory Errors on Platform Analytics List Visualizations - Known Error

Out‑of‑Memory Errors on Platform Analytics List Visualizations Description When a Platform Analytics workspace loads a list visualization with 'maximum rows' configured to be a very high number leads to exhausting the JVM heap and causing node restarts and Out‑of‑Memory errors.

Note:- This property is actually the number of records to display per page and not the total number of records to be fetched by the list.

Steps to Reproduce

1. Open a Platform Analytics workspace and add a List visualization that queries a table with a large record count. 2. Set the visualization’s **Maximum rows** field to a high number (e.g., 10 000). 3. Load the visualization; the client sends a POST to /api/now/uxf/databroker/exec. 4. Observe the node OOM and restart events caused by the Rhino parsing of the large JSON payload. Workaround If the data visualization plugin version is 28.5.0 for Zurich 0r 29.1.0 for Australia then the issue could be coupled with another PRB - PRB2038106 - if this is the case please refer the KE - https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3100924 If the plugin version is different than the one mentioned above or if the issue persists after applying the workaround for PRB2038106 then there is a list data visualization where the value 'maximum rows' property is very high, Ideally it should be blow 100 (10-20 is the recommended range) - This property is actually the number of records to display per page and not the total number of records to be fetched by the list, so this could have been misunderstood and configured wrongly.