Happening to me too. Looks like this happened earlier today and fixed - and broke again. There’s a post on lodestone about the issue earlier today - same error message happening now