@site5supersam @site5support @site5 Actually without being updated or notified, it looks like it was fixed! So we're good!