USer Story: users are experiencing sporadic failures during the startup of Magnolia instances, specifically on faster machines. The issue is related to a delay in applying server configuration or order of applying certain part of the configuration. This started to appear after the upgrade to Magnolia version 6.2.38, although previous versions also can be affected

As described here: https://magnolia-cms.slack.com/archives/CC1GVEGFP/p1694701640514539

TL;DR (apchelintcev)

as I see it - the problem is that core brings in the correct server config, but there’s a 1 second gap before it is applied and new beans are produced on its basis, which may become visible on the newer/faster machines

re: fix - guess we could slash the delay during the install time to smth really small, and/or manually re-trigger the sensitive beans directly from core module installation phase

Dev note:

• to reproduce the issue steadily change this delay to 5000.