Select to view content in your preferred language

Filter data actions causing site to freeze

50
1
4 hours ago
Labels (1)
Michal
by
New Member

I've been developing a data dashboard through experience builder, and I've noticed that ever since the most recent June 2026 update, clicking the "Filter data records" button when adding an action freezes the whole site for an extended period of time. This seems to be somehow correlated with the total size of the datasets you have loaded into experience builder as fewer/smaller datasets reduce the time which the site is unresponsive. Prior to this update when I was adding a filter data record action it would be relatively instant (<1s) to load the panel which allows you to select the action data whereas now it is taking me up to 12mins just to load this one menu. 

My best guess of what might be causing this is that the site is loading every dataset or layer from all of the different pages all at once into memory, causing the site to freeze. And since we have several web maps added each with several large layers, this results in a severe stall until everything is parsed. I'm not actually sure why this is happening, it could also be something else like a loop within a React component; however, freeze time correlating with dataset size would support my guess. There is also no change in my system resources before, during, and after the freeze meaning that this is stemming from an issue with the site itself. 

To reproduce: On an experience builder page that has a web map containing several data layers, add a chart such as a pie chart and visualize one of the layers from the web map. With the chart selected, go to the "Action" tab and under "Message action" click "+ Add a trigger" and select "Record selection changes". Then click "+ Add action">"Data">"Filter data records". Once this button is pressed, the site will freeze for a period of time dependent on how much data you have in experience builder.

0 Kudos
1 Reply
Ke_Xu
by Esri Regular Contributor
Esri Regular Contributor

Hi @Michal,

We couldn't reproduce this issue with in-house data. Could you help provide an app for us to troubleshoot?

 

Thanks,

Ke

0 Kudos