I have a weird situation, where if I turn on the debugger, Adobe Launch will show a rule as firing but in actuality, it didn't execute the JS code (in the action) and no error was thrown? I put console.logs in the code and they never happen. This doesn't happen all the time, but it happens enough where it is an issue. This happens to more than one rule. Any ideas on what can be causing this and how to debug/fix it? FYI... this isn't conditional code; one rule creates a JS object and the other one starts a page load performance timer.
The only variation with our implementation is that we don't load the primary Launch library until we get a response back from a geolocation API but it is very fast and still don't understand why this type of issue would happen?
Thanks,
MJ
