Spent a day and a bit configuring a Query Widget in an Experience Builder my team is creating for our end users. Got everything in the Query Widget working fine and come in the following Monday morning after the weekend and load up the Experience Builder in view mode to find that a few (3-5) layers are throwing errors in the Query Widget and say "Data is inaccessible". I turn on visibility for those layers in the map and they seem to work fine (symbology, labelling, pop-ups all working). So I refresh the Experience Builder view and those layers are fixed now, but now 3-5 other random layers show the same issue as the previous ones did. After refreshing several times the same thing would happen (previous layers worked fine again in the widget but a new set of layers said data was inaccessible and showed a big red 'X'). Then all of a sudden one refresh everything was working fine again and subsequent refreshes showed no errors.
We are working with Registered/Referenced data on our Portal we share from ArcGIS Pro (mostly SQL data, eGDB, some shapefiles, but all sources are registered with the server). We are using a dedicated instance configuration option as opposed to shared instance when we shared our layers to Portal as we expect heavy usage out of this app and its data when it's complete and sent to our end users. I am wondering if this error shown by the Query Widget could have something to do with the dedicated instance having a slower "cold start" than a shared instance, or if anybody has had a similar issue and has any insights. We would rather our app not throw random errors when it is in operation across our organization.
