Experience Builder Saving Errors

[AndrewSpencer]

I'm starting to look at recreating our WAB applications in Experience Builder but having lots of errors saving. Specifically I'm getting errors when configuring what appears to be too many attribute tables in the Tables widget and/or too many queries in the Query widget. I don't believe its an error in my map data as I can add any number of different tables, or different queries, until I reach what appears to be a limit (currently 4 queries and 6 tables). The number doesn't always seem to be consistent, but it does always generate saving errors at some point. My map has 11 layers and I want the ability to view them all as a table table, and to configure queries against each of them. Worthwhile pointing out that there's no issue doing this in WAB and also that the EB Map Layers widget doesn't have the option to view the layer attribute table so the layer has to be pre-configured in the Tables widget.

Any ideas greatly appreciated....

[AndrewSpencer]

It appears that the saving errors might be related to to our corporate environment, or even our version of Edge, as saving is fine when accessed from elsewhere. If I I manage to discover the specifics I'll update here.

[AndrewSpencer]

Problem solved - at least partially. We now have a workaround - in Edge Devtools  > Network > Throttling if I set to Fast 3G I'm able to save without error. It's not clear yet if the root cause is the browser, our environment, or the platform.

[hherrmann_coj]

Have you used EB at all in Chrome?  I'm starting to dip my feet into Experience Builder currently and I seem to constantly get "save error" and it's random.  It almost feels like EB timing out and I have to reload the page which causes me to lose all of my edits/changes.  I have tried to reproduce the error but since it appears so random, I have been unsuccessful in doing so.  I'm going to try digging around in Chrome dev tools and see if I can find a similar setting that you used for your work around.  

[JeffreyThompson2]

I have an open support ticket about this problem. It has not happened to me for a long time. I haven't been thoughtful enough to record any console errors when it's happened. Do you get an error in your server console? Could you take a screenshot?