Type Into Timeouted Even Though the Input Box Is Seen

Help
,
1

When:
Sometimes (about 1 in 10).
Usually happen when the web loads slow.

Details:
A simple automation to login to website.
The automation works most of the time, so I don’t think it has problem with selector.
But sometimes, when the website loads a bit longer than usually,
when the input box finally came out, robot didn’t type anything,
then timeouted about a minute after (set about 3 minute timeout on that).

Question:
Anyone having a similar experience? Any idea to make the typing more robust?

Tried to no avail:
Activating the browser.
Set longer timeout (now 3 min).
Using Simulate Type (and Send Windows Message and none of them too)
WaitForReady : Complete

2

I would try image exist and delay activity in loop till get the image exist true.

3

Hello @rajeshprabhu_gp, never tried checking with image exists before.
Will try to check if it makes any difference after checking login button image or so on.
Thank you for your reply.

4

You can even try with “element exists” or “wait element Vanish” Activitys

1 Like
5

Hello @hemanth_chinna, thank you for your reply.
That implies that the Type Into itself doesn’t really recognize well when an element appear longer than it should.

I thought Type Into works like:

  1. Delay as long as DelayBefore
  2. Check WaitForReady (if complete, wait till the whole page to load)
  3. Then, until TimeoutMS is reached, will try unceasingly to Type Into the element.

But is seems like:

  1. Delay as long as DelayBefore
  2. Check WaitForReady (if complete, wait till the whole page to load)
  3. Will try to Type Into, but when not found will just wait till TimeoutMS is reached
6

Try to put a try-catch inside a loop/counter, with a hover activity, checking if the field is present. If true, then click on the field first before typing.