So I don’t think the Unable to resolve class internal.GlobalVariable error is anything more than a non fatal warning if you see the error right before the lines below in the console output like so:
katalon | /%tmp%katalon_execute%project%your-katalon-project.prj/Include/scripts/groovy/Steps.groovy: 21 Groovy:unable to resolve class internal.GlobalVariable
katalon | Generating global variables...
katalon | Project 'your-katalon-project' opened
However if you get an error complaining about resolving global variables during a test case, then your project has been corrupted somehow and the global variables are not compiling correctly. Dunno what your issue is. I have had this happen and the error prints out like a normal Java stack trace during the execution of a test case.
For many people, including me, the error is probably something else and it seems like the warning about Unable to resolve class internal.GlobalVariable is an actual error causing us pain, probably not.
Reading through this thread you will realize a whole lot of people having issues with specifically running tests through the console and especially Docker. This thread, in my eyes, has become the default thread for, "I don’t know what happened but I saw Unable to resolve class internal.GlobalVariable in the terminal output.
If by chance you are git-ignoring your Profiles/ dir and/or editing your *.glbl files outside of katalon, I’m pretty sure this is your actual issue. If so, here is another topic I created to discuss profiles and console mode issues.
Good luck!