Every login page is unique... just like a snowflake.

While we try to make our login feature work automatically with all the login pages we come across, you might find a specific case that unfortunately fails.

If this is the case, there are a few things you can check.

When the login procedure fails, we record the step where the process failed in our error message, for example: "Browsing - Login through https://www.example.org/login failed (step: submit button failed)"

Below is a list of the steps we go through and what you can do if the error message indicates it failed at that point:

  • Reveal modal: (Only when "Login form reveal button" CSS selector is set) The button couldn't be found, either because the selector is incorrect or the button is not visible.
  • Fill in username: (Only when "Username" value is set) Either we couldn't find the input, or we couldn't click on it and enter the value.
  • Going to the next step: (Only when "Form has two steps" is checked) The next step button couldn't be found, either because the selector is incorrect or the button is not visible.
  • Fill in password: Either we couldn't find the input, or we couldn't click on it and enter the value.
  • Submit button: The submit button couldn't be found, either because the selector is incorrect or the button is not visible.

If the username, password, next step or submit steps fail, it's probably because the input or button is represented differently from common implementations (for example, we found some cases where the submit button was actually a regular <a> element). 

You can inspect the HTML of the login page to troubleshoot this. Try to find the element related to the step that failed (i.e. submit button). If it has an ID or a set of CSS classes you can try setting the corresponding CSS selector value in the new sitemap form (i.e. "a#submitLoginForm").

Did this answer your question?