@cliff538 Nope, I think it was some temporary bad data that was cached on our side. I’m fixing one problem now that will make this more robust in the future.