Overwriting a layer from Pro is removing it from my web applications

[KellyMarton]

I have been loving the ability to overwrite a layer in AGO using Pro (right click on the layer -> sharing -> overwrite web layer). It used to seamlessly update the data in a layer and continue to function in whatever apps I had them in without hurting the symbology or pop up behavior, which kept me from having to reconfigure every time I updated data as I used to when I was using ArcMap.  However recently, when I follow this process and open the applications where I expect to find an updated layer, I get an error that says "The Layer, (name), cannot be added to the map." The layer itself has been updated and can be readded, but I lose all of the functionality and display settings I had programmed into my WebApp Builder apps. Why is this happening and is there a way I can avoid it? 

[MichaelVolz]

Did you change the format of the pop-up using the more complex method?

[KellyMarton]

No, they are very standard pop-ups, symbology, and widget configurations (filters and queries). The fields are not changing in the layers when I overwrite them. They are projects that I specifically designed for this workflow as data is added or updated over time. I have two separate projects where this has become an issue within the last month. 

[KellyMarton]

I should add that the layer is actually being removed from the web map, which is causing the issue with the WebApp Builder app. I can re add the layer to the map and reconfigure everything again, but that defeats the purpose. 

[MichaelVolz]

Are you saying that the "layer -> sharing -> overwrite web layer" process in Pro that used to work is now removing the layer from the web map?  If so, that seems like quite a big bug as it will create a significant amount of extra work when making changes to layers that are used in WebApp Builder apps.

I would like to know if ESRI considers this to be expected behavior.

[KellyMarton]

Yes, that is correct.