So how the whole thing works is by listening for when a page is done loading, filling a bunch of fields out and clicking a button. The problem is there's no one "this page is done loading" event that Chrome exposes. A "page loaded" event is raised each time something on the page is done loading , which in the case of newer sites is a lot of things since a lot of stuff is loaded asynchronously. The problem with JL and sometimes BA to a certain extent is that their search page does I don't know what exactly but makes it really slow.

If you go to the JL site manually and load their partner award search page, you can see it in action. It takes a few seconds for the page to be usable after it looks like it's done loading. The problem here is that if this "I don't know what it's doing" takes a long time, which can happen if the site is slow, there's a timeout in the app that says "after X seconds and I can't recognize this page since I can't recognize the elements on the page", assume this is an error.

This happens sometimes when the JL site is really slow but it can happen to all of them.