Symptoms:

Example: You're working without a proxy. When the debugging mode is on, the page downloads correctly, however it still cannot find the element. This happens each time (and not every other time).

Reasons:

The element's address was recorded incorrectly.

Solution(s):

Try to record the template again. It is not necessary to re-record the whole template, only the needed part. From the recorded part, you simply copy the branch that had the error. You can detect the error-containing branch in the log (when debugging). The ID of this branch in registered in that log in case an error occurs.

Symptoms:

Example: Working with a proxy, the error occurs every other time I try to execute the template.

Reasons:

There is not enough time for the web page to get downloaded through the proxy.

Solution(s):

Insert a pause after each action leading to a new page. Or simply select better proxies.

Symptoms:

It will not recognize CAPTCHA at all or it writes sorry instead of CAPTCHA text.

Reasons:

CAPTCHA recognition is configured incorrectly. Otherwise the CAPTCHA recognition service is overloaded.

Solution(s):

If you are using manual recognition services, then the first thing you should try to do is to shift CAPTCHA recognition to the manual entry mode. If the error disappeared, then there is a problem in the service settings and therefore beneficial to browse the CAPTCHA recognition setting section. Try to change the service or increase cost for recognized CAPTCHA - this will give you advantages when the service gets overloaded. If the error still persists, then there is a problem within the CAPTCHA search. Read recommended documentation to learn how to solve this issue.

Symptoms:

When switching to manual recognition mode, it provides the wrong image (usually the one next to CAPTCHA).

Reasons:

The element number for CAPTCHA search has glorked/gliched itself (recorded incorrectly or the web page has changed).

Solution(s):

Try to re-record this part of the template. Otherwise open Template Editor, highlight the branch responsible for CAPTCHA recognition and find a table in the Element Properties Panel. In the last column of this table you will see figures. Try changing them beginning with the top line by adding +-1 and see if the produced image has changed or not. If it has, then this is the CAPTCHA found line. Play with the figure: +-1 or +-2 (but not less than 0) and sooner or later you will hit CAPTCHA. Basically this changes the number of the image on the web page that is considered to be CAPTCHA. If you get an image located below CAPTCHA on the web page, decrease the number, if the image appears above CAPTCHA -increase the number.

Files should be saved in Unicode. Open the file with the text editor and when saving select the UTF-8 coding.