Issue  

Tables with pagination become unresponsive and cause Pega Platform™ to enter a stale state immediately upon navigation.

Symptoms and Imact

Tables configured with pagination fail to function correctly during page navigation, leading to stale state errors and disrupting normal workflow and case processing.  

Browser consoles may display "[goingBusy] already busy (startClientBusy)" indicating a JavaScript deadlock where the busy state never clears. Multiple row selection is not enabled on these tables.  

The issue does not occur when "Generate Optimized Code" is disabled.  

 Steps to Reproduce 

1.  Create an optimized table.
2.  Include an Embedded Section in a column of the optimized table.  
3.  Make sure that the Embedded Section contains complex data instead of direct usage of simple UI elements.  
4.  Perform any table operations on the table in UI.  Result: Pagination, Filtering, Sorting, and Grouping operations won’t work in the optimized table. For example, click the pagination controls (page 2, 3, next, etc.). The application becomes unresponsive.  

Root Cause   

This is a known limitation. 

Optimized tables in Pega Platform™ utilize a template-based client-side rendering model, which provides enhanced performance and user experience. However, when Embedded Sections are used within table columns, they introduce server-rendered UI logic that conflicts with the client-side rendering model. This conflict can cause table operations such as sorting, filtering, and pagination to fail or behave unexpectedly. 

Solution  

 To restore table pagination functionality, we recommended implementing one of the following configuration approaches: 

1. Convert to Non-Optimized Table: Modify the table configuration to use the traditional non-optimized rendering model, which fully supports Embedded Ssections. 

2. Remove Embedded Section Columns: Remove Embedded Section columns from the optimized table. 

3. Simplify Column Configuration: Replace Embedded Sections with direct property references or auto-generated controls that are compatible with the optimized table rendering model. 

References

Creating a table layout without code optimization 

Creating a table layout with code optimization 

Limitations of optimized tables sourced from queryable Data Pages 

Configuring table operations and toolbar 

Why role="presentation" exists in the markup of non-optimized tables in Traditional UI