Interesting, so this happened to somebody else seven months ago. I wonder why it is just affecting me now.
I appreciate the suggestion, and it may be correct that adjusting the workflow to newer tools is necessary. However, I still want to express that it isn't a wonderful solution (please note that this incoming rant is not directed at you, Marco - I really do appreciate your reply.)
We spent a good bit of time configuring the Web AppBuilder template to the way we wanted it, recorded several "how to use our maps" videos explaining the tools and the placement on the screen, and some of those that we work with expect maps in a specific format that is difficult to duplicate in Experience Builder, for example. Obviously, the writing is on the wall for Web AppBuilder and anything else built on the Map Viewer Classic platform, but if the solution is to adjust the workflow to newer tools, then these older ones are effectively dead already, because the output is unusable.
If Esri intends to fix this bug, that would be useful to know.