AHHHH the spinney wheel of death. Sadly, I know it well. As a team we saw this after new notification updates were pushed to our instance. None of us ever saw it at the same time or consistently and it seems to be browser agnostic. So super frustrating and hard to pinpoint.
For better or worse I don’t take broken as a final answer so….
We went round and round with cache clearing and browser installation and then with Docebo support (who also could not replicate it). Finally got to a level 2 support person who after a few rounds of screen shots and broswer log files suggested we have our IT department unblock a number of and domains from our firewall software.
the list had some of the largest domain carriers on the net, so initially a hard no from IT (unblock *.amazonaws.com? yeah… right)
BUT after some port sniffing (it’s a thing), we unblocked the following and the problem seems to have gone away
*.docebosaas.com
*.dcbstatic.com
*.docebo.cloud
POSTSCRIPT- Make sure you create a support ticket with Docebo about it. The new module has issues which are not isolated and they need to hear from people before they can correct it.
Hope this helps.