Certain popup window makes the timeout take much longer than the default value(30 seconds)

Hi,

Certain popup window makes the timeout take much longer than the default value(30 seconds)

I already created a topic about this on nov 27th.
Check topic and the troubleshooting made:

Have anyone experienced something similar?
UiPath team, do you have and clue what could cause this?

Hi,

If your popup is created by JavaScript, the following topic might help you.
In that case, the activity for showing the dialog (not the click activity for button) is waiting response from JavaScript. Setting HardwwareEvent in the first Click activity solves this matter.

Regards,

Hi @Yoichi

I have tried to use “Hardware Events” as the input mode in the activity just before the popup appears, without any success.

image

Directly after this click activity has been executed if the following popup appears:
image

The timeout before System execption was 3 min and 31 seconds this time.

I have also tried to make the activities after the popup use “Hardware events” and also that the “Use Browser” Scope uses it without any success.

The strange thing is if I use the classic activities the time out is much closer to 30 sec as described in my previous post right here:

@Yoichi

There are workarounds.

  1. Try to handle most of the popup windows with element appear/exists.

  2. Pick/pick branch where I have a delay + Throw:

But I still would like to know what is causing the issue.
Unsure if it is the activity before or after the popup is waiting on some kind of completion?
But the UiPath REF I feel should still handle it as a SE with the default 30 sec timeout, but im maybe wrong.

Hi,

From this, can you try SingleWindow at WindowAttachMode of UseApplicationBrowser activity because SingleWindow mode is similar with classic Attach/Open Browser activity?

Regards,

Hi,

I have tried this now without any success. UseApplicationBrowser/NApplicationCard was modified before and after where the popup window would appear. Also tried with Hardware events and chromium API, no success.