If this was expected behavior, then please close this bug report.

To be clear, you tried viewing a page like https://office.wikimedia.org/w/index.php?title=Does_not_exist&action=edit&redlink=1, and instead of a wiki interface, you got an error page like the below?

If so, this probably wasn't related to VisualEditor (or MediaWiki), I think these errors are generated by load balancers or something. I also don't see anything that would point to VisualEditor in the error logs around that time (Logstash).

In T163359#3198637, @matmarex wrote:

To be clear, you tried viewing a page like https://office.wikimedia.org/w/index.php?title=Does_not_exist&action=edit&redlink=1, and instead of a wiki interface, you got an error page like the below?

If so, this probably wasn't related to VisualEditor (or MediaWiki), I think these errors are generated by load balancers or something. I also don't see anything that would point to VisualEditor in the error logs around that time (Logstash).

No, I got a pop-up dialog box (browser-style, not one of VE's own pop-ups) on top of the VE window, and it was much less verbose than the usual 503 landing page. I believe it said something like "Error: 503 [something something]" - 4 or 5 words total. Apologies for not having a screenshot or a better memory of it - at the time I assumed it was expected behavior during the planned outage, so I didn't think much of it until Whatamidoing told me otherwise afterward.

Did it look like any of these three?

Option 1

Option 2

Option 3

In T163359#3201790, @Whatamidoing-WMF wrote:

Did it look like any of these three?

Option 1

Option 2

Option 3

Definitely not Option 1. I believe it was like Option 3, though I wouldn't swear on my life that it wasn't Option 2.

In T163359#3201744, @Kbrown wrote:

No, I got a pop-up dialog box (browser-style, not one of VE's own pop-ups) on top of the VE window, and it was much less verbose than the usual 503 landing page. I believe it said something like "Error: 503 [something something]" - 4 or 5 words total. Apologies for not having a screenshot or a better memory of it - at the time I assumed it was expected behavior during the planned outage, so I didn't think much of it until Whatamidoing told me otherwise afterward.

I guess it's a 503 from one of the API calls we use then, rather than the page itself. Still, probably not a VE or MW bug, but something with the server setup – I don't really know if these errors would be expected during the switchover. Thanks for responding.