The issue was found by @slawek during 1.16.0 sanity checks. Source
I observe these error events:
However, it seems to be a problem with the demo environment's misconfiguration.