For this one, I probably wouldn't answer.

The reason is that the issue is effectively solved already:

The commenter explained the likely cause (refresh behavior causing client issues).

The original poster tested a change based on that advice.

The original poster replied:

"Wow, you helped me a lot. I moved the refresh from the event to the datagrid, now the problem is solved."

That's essentially confirmation that the solution worked.

If you absolutely want to add an answer so there's an official answer on the thread, keep it short and summarize the resolution:

The issue was caused by refreshing data through the page event mechanism. Although it worked initially, repeated refreshes eventually caused client-side errors in the React client.

The fix was to move the refresh logic to the Data Grid/Data Widget itself instead of triggering it from the page event.

After moving the refresh to the grid, the unexpected errors stopped occurring.

If anyone encounters similar stack traces involving:

Plain Text

retrieveByXPath

and intermittent client-side errors after repeated refreshes, check whether the refresh is being triggered from a page-level event and consider refreshing only the specific widget or data source that needs updating.

But honestly, I'd spend time on another unanswered question because this one has already been solved and acknowledged by the OP.