Legacy Knowledge Base
Published Jun. 30, 2025

"Uncaught (in promise) ReferenceError: global is not defined" or "Error: Load timeout for modules" errors reported in the front end.

Written By

Ethan Wei

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • There are "Uncaught (in promise) ReferenceError: global is not defined" or "Error: Load timeout for modules" errors reported in the browser console and cause some abnormal behavior like some buttons disappearing, form not loading, etc.
  • The issue mainly affects sites where Google Tag Manager (along with Linkin script) is used.

Environment

  • Liferay DXP 7.1
  • Liferay DXP 7.3

Resolution

  • This was fixed by LPS-196120, please open a help center ticket to request a hotfix.

Additional Information

  • To determine if this is the issue the user is experiencing, follow the following steps:
    1. Go to the page where the issue can be reproduced.
    2. Open the Developer Tools in the browser -> Switch to Network tab -> Refresh the page.
    3. Search for "insight.min.js". 
      1. From the Initiator tab, we can see that this script is from GTM(GoogleTagManager).
    4. Blacklist the domain "snap.licdn.com" in hosts file to see if the form/button loads as expected.
      127.0.0.1 snap.licdn.com
  • If the page can be loaded correctly after this, then the issue described in this article is the issue that user is experiencing.

 

Did this article resolve your issue ?

Legacy Knowledge Base