[erro] open' failed. No page load event detected after 10 seconds. Error detail: still same ipc secret

Hi,

I know this topic has been discussed many times. But may be I have something new.

I am with the new version of the RPA 6.2.2. I don’t know if the problem occured before since I am still testing the product and I am a newbie on ui.vision !

I have this code to retrieve my ip. The website https://api.ipify.org/ returns an only value, the ip :

{
  "Command": "open",
  "Target": "https://api.ipify.org/",
  "Value": "",
  "Description": ""
},
{
  "Command": "pause",
  "Target": "5000",
  "Value": "",
  "Description": ""
},
{
  "Command": "storeText",
  "Target": "xpath=//pre",
  "Value": "ip",
  "Description": ""
},

The website https://api.ipify.org/ is sometimes a bit slow to open the page. In this case I have this “open’ failed. No page load event detected after 10 seconds. Error detail: still same ipc secret” error.

So I checked my !TIMEOUT_PAGELOAD which is 55 seconds in the settings. I did as well an echo of the value in the macro and it is definitly 55 sec.

To see the problem I call the same macro (via command line) about 20 times (closing the RPA between but not the browser). In a row, it happens once or two times. Sometimes it works like a charm. It depends on the ipify.org response. So I spent half an hour looking at my screen :wink:

When the macro open https://api.ipify.org/, I see the seconds scrolling (1, 2,…) something like “wait 3s (55)”, with 55 the timeout_pageload. So usually it succeeded, but when the page has some difficulties to open (the Firefox is waiting : with an hourglass in the tab), seconds pass and at “wait 11 sec. (55)” the error happens.

So no matter the value I have in !TIMEOUT_PAGELOAD, there is “another” time out (which one ?) of 10 seconds. The only 10 seconds I have is !TIMEOUT_WAIT which is not supposed to interfere.

So I have the feeling that !TIMEOUT_PAGELOAD is not doing its job. When the website is slow, I have nothing in the page so for sure the page is not loaded.

So if it is a bug it is a bit annoying because 10 seconds it is short. In this case the problem will be easy to reproduce (with a very slow website or even with : https://api.ipify.org/.)

But probably it is a newbie mistake, so enlighten me ! Because it is really blocking…

Thanks.

Eric.

This is very interesting info! I will be testing this further.

But why is it blocking? Workaround: If it happens, you can just restart the macro, or?

Hi,

Thanks for your interest.

Blocking because it could happen in a middle of a macro which has done half the job and leave the data in an inconsistent situation.

For example to fill a website with data, one cannot just restart the macro, one will have duplicates. The only solution is to do a test on this error, and provide for manual intervention so as not to chain another macro which depends on the result. For sure, We know that the page will open but if we only have10 seconds before it goes in error, it is blocking for us.

Best regards,

Eric

Hi,

I can now reproduce the bug (?) every time. Thanks to “https://deelay.me/30000/https://api.ipify.org/” in my test code.

deelay.me : “With this proxy you can simulate unexpected network conditions when loading a specific resource.”

So the time out which produce the error is indeed !TIMEOUT_WAIT.

So if I open “https://deelay.me/30000/https://api.ipify.org/” with a !TIMEOUT_PAGELOAD=55s and a !TIMEOUT_WAIT=10s, the error occurs at Wait 11s (55).

If I open “https://deelay.me/30000/https://api.ipify.org/” with a !TIMEOUT_PAGELOAD=55s and a !TIMEOUT_WAIT=45s, there is no error and the count (number of seconds) continue beyond 10 sec, and it works.

By the way I found deelay.com in the page : https://ui.vision/demo/pageloadtimeout. But there is a bug in the page. The links are :
http://deelay.me/1000/http://deelay.me/img/https://ui.vision/Content/Images/delay1s.png

They should be :
http://deelay.me/1000/https://ui.vision/Content/Images/delay1s.png

Regards,

Eric.

Thanks a lot, this test is very useful! => We will fix this with the next update.

Hi,

You’re welcome !

Regards,

Eric.