Find it odd that this only started happening after an upgrade. Does this happen every single time?
Have you tried burning in LaserGRBL to see if you get the same results? Or downgraded back to previous version of LightBurn?
There was another recent thread about alarm stops and a parameter to adjust sensitivity but that was for a different alarm and different firmware version.
Error:9 G-code locked out during alarm or jog state - LightBurn Software - LightBurn Software Forum
You may want to consider upgrading firmware in either case as there are notes about updates to g-shock sensor algorithm to reduce false positives. It’s not clear to me that’s what’s happening here but it’s a possibility.
@OrturTech might be able to provide specific insight.