[Bug Report] Triggering a console lockout from aRFR app.

I created a macro that contains Console_Lockout. When triggering this macro from the aRFR app (either via direct selects or typing on the keypad), everything initially looks correct. However, after the initial lockout has been cleared via Shift+Escape on the computer running EOS, EOS will lockout again every time that any inputs are made on the app.

Eos version 3.3.5.69 on Windows 11 Nomad (with or without actual nomad dongle)
aRFR version 4.1.7 on Google Pixel 7a

Related