@mjtsai This has been addressed. It was unfortunately the intersection of a latent client-side bug (been there for a long time) and a change in a server-side policy that exposed the latent bug; the issue was not connected to the monthly update and Liquid Glass changes. It took more time than desired to identify the server-side change as the root cause.