We recently upgraded to Pega 2023.1 and we’re getting sporadic reports of the “can not render section” error. I haven’t found much in the way of error logs to quantify. Clicking on a refresh icon usually works. Have other folks seen this as well? I’ve seen that error in the forums from 2015-19 but not as much recently.,
@DPCLARK12 please log a support issue via the MSP so that our GCS team can help investigate.
I have found one other client with an issue on '23 where the problem is grid event is called on the wrong context. In the underlying grid design is causing a switch of thread or context. Because of that, it is unable to find the proper section in the particular class. A work-around for this issue cannot be found without underlying fixes to the design.
More info: Clicking in the space between the column title (which allows sorting) and the filter button on a table column header for an intent task causes an error: In the UI: The table disappears and is replaced by “Can not render section” In a tracer: FAIL - Failed to find instance XYZ-Work-Interaction-Call.MemberClaimsInquirySearch of type Rule-HTML-Section. where XYZ is the property the table data is based on. This causes the end-user to have to refresh the page while on a call if they miss clicking precisely on the sort or filter areas of the header
BUG-846347 will fix this issue and is currently targeted to be provided in the Pega 23.1.2
Your issue may be different but you would need to investigate together with our support team.
Once you have logged the support issue, please come back here and post a reply with the INC id so that we can help track this.