Only time I've ever run into XML hell on Confluence is when dealing with imported pages. Their automated import tool is neat, but it leaves you with some cleanu

Only time I've ever run into XML hell on Confluence is when dealing with imported pages. Their automated import tool is neat, but it leaves you with some cleanup to do since not all of the markup from $wikiPackage transfers cleanly to Confluence macros. Combine this with the fact that there's no error handler for broken pages - if the XML that makes a page work is invalid on the back end, the page just straight up won't render and has to be fixed another way. (Which sucks, but as I said, this is not a thing most people will ever encounter). It's not possible to generate invalid XML using the WYSIWYG editor, but plenty possible if you're using either the code editor, or plugins that do strange things. The logs are chatty as hell and you'll generally get stack traces for even completely benign problems/notices. That's one thing I wish they'd deal with, but it's pretty minor. If you're getting error-level stack traces and XML nonsense on a daily basis, something is terribly wrong in your instance. That is simply not standard behavior, and I'm kind of curious what their support people are telling you. (Shoot me an email if you're comfortable doing so - I may be able to help you out)