Apparently it's back, now affecting both local and deployed code all of a sudden

@Robert Welch 👋 This issue has been solved, are you still seeing this?

I will test again tonight and let you know