- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
11-23-2021 11:56 PM
We have created quite a few web-apps now using the instructions here. https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASIMP/psm_WebApplication.htm
Most of them work fine.
Two recently created connectors take a really long time between the steps listed in WebFormFields. I can't figure out why this would be happening as the values are quite simple.
Slow connector 1:
user>{Username}(SearchBy=id)
passwd>{Password}(SearchBy=id)
ext-gen8>(click)(SearchBy=id)
buttonFixed>(Button)(searchby=class)
Slow connector 2:
email_verify>{Username}(SearchBy=id)
next_button>(Button)(SearchBy=id)
password_login>{Password}(SearchBy=id)
no_captcha_submit>(Button)(SearchBy=id)
Slow connector 1 performs the first 3 steps very quickly, then pauses. I can't tell for certain if the delay is before clicking the button, or if the delay is a slow http response after clicking the button.
Slow connector 2 has a long delay between clicking next_button and entering the password_login.
As you can see, there is nothing in the code to cause a delay. What else could be causing this strange behaviour?
Note, this is not the same issue as Handling slow login with PSM Web Connector (force.com)
11-24-2021 01:33 AM
Lower the ActionTimeout value and try again. Then raise the PSM debug level and check the logs for that connection. It should show what the PSM WebApp dispatcher is waiting for between actions.
11-25-2021 09:56 PM
Very helpful thanks. Here are the problem bits:
For Slow connector 1:
[26/11/2021 | 16:25:32] | :: | PSMDU019I Dispatcher trace message: [WebElementWrapper :: WaitUntilElementIsNotVisible -> Waiting for element ext-gen8 to erase from page.]
[26/11/2021 | 16:25:35] | :: | PSMDU018E Dispatcher error: [WebElementWrapper :: WaitUntilElementIsNotVisible -> Failed moving to the next page. Element was not erased from the page. Exception Details: OpenQA.Selenium.WebDriverTimeoutException: Timed out after 2 seconds
at OpenQA.Selenium.Support.UI.DefaultWait`1.ThrowTimeoutException(String exceptionMessage, Exception lastException)
at OpenQA.Selenium.Support.UI.DefaultWait`1.Until[TResult](Func`2 condition)
at CyberArk.WebAutomationUtils.WebElementWrapper.WaitUntilElementIsNotVisible(Int32 actionTimeout)]
ext-gen8 is a checkbox. It is not supposed to be erased from the page. I don't see anything in my code that should be causing the script to wait for that. Should I be using an action other than 'click' for a checkbox?
For Slow connector 2:
[26/11/2021 | 16:24:37] | :: | PSMDU019I Dispatcher trace message: [WebElementWrapper :: WaitUntilElementIsNotVisible -> Waiting for element next_button to erase from page.]
[26/11/2021 | 16:24:40] | :: | PSMDU018E Dispatcher error: [WebElementWrapper :: WaitUntilElementIsNotVisible -> Failed moving to the next page. Element was not erased from the page. Exception Details: OpenQA.Selenium.WebDriverTimeoutException: Timed out after 2 seconds
at OpenQA.Selenium.Support.UI.DefaultWait`1.ThrowTimeoutException(String exceptionMessage, Exception lastException)
at OpenQA.Selenium.Support.UI.DefaultWait`1.Until[TResult](Func`2 condition)
at CyberArk.WebAutomationUtils.WebElementWrapper.WaitUntilElementIsNotVisible(Int32 actionTimeout)]
The button does disappear from the visible screen, but remains in the code. i.e. it transforms the page, not moving to a new page. I'm not sure what can be done about that. Is there another way to interact with buttons that doesn't anticipate the button being erased?
At least with actionTimeOut set to 2 instead of 20, the wait time isn't so extreme.
12-20-2021 09:38 AM
I have the same problem. The tool always expects the element I click to disappear, which is not always true. So in a lot of scenarios, the plugin just takes a long time to execute because it waits for the timeout every time I click something on the page.
Is there any option to disable this "Waiting for element to erase from page" check for some of the elements I click on?
Thank you
12-22-2021 10:59 PM
I have not found a solution. Reducing the timeout action to 2 seconds has been 'good enough' for the customer. I still think it's a terrible solution.
08-23-2023 05:00 AM
Hi
I have the same problem , were you able to get a way around this ?
10-02-2024 02:24 AM
Also facing the same problem. Selenium expects the web element to disappear causing long delay. This can be adjusted by setting `ActionTimeout` to a lower value i.e 5 or 2 in the CC.
From logs:
[02/10/2024 | 11:19:28] | :: | PSMDU019I Dispatcher trace message: [WebElementWrapper :: Click -> START]
[02/10/2024 | 11:19:28] | :: | PSMDU019I Dispatcher trace message: [WebElementWrapper :: Click -> Clicking on element 'radius_auth']
[02/10/2024 | 11:19:28] | :: | PSMDU019I Dispatcher trace message: [WebElementWrapper :: Click -> Clicked successfuly on element.]
[02/10/2024 | 11:19:28] | :: | PSMDU019I Dispatcher trace message: [WebElementWrapper :: Click -> END]
[02/10/2024 | 11:19:28] | :: | PSMDU019I Dispatcher trace message: [WebElementWrapper :: WaitUntilElementIsNotVisible -> START]
[02/10/2024 | 11:19:28] | :: | PSMDU019I Dispatcher trace message: [WebElementWrapper :: WaitUntilElementIsNotVisible -> Waiting for element radius_auth to erase from page.]
[02/10/2024 | 11:19:39] | :: | PSMDU018E Dispatcher error: [WebElementWrapper :: WaitUntilElementIsNotVisible -> Failed moving to the next page. Element was not erased from the page. Exception Details: OpenQA.Selenium.WebDriverTimeoutException: Timed out after 10 seconds
at OpenQA.Selenium.Support.UI.DefaultWait`1.ThrowTimeoutException(String exceptionMessage, Exception lastException)
at OpenQA.Selenium.Support.UI.DefaultWait`1.Until[TResult](Func`2 condition, CancellationToken token)
at OpenQA.Selenium.Support.UI.DefaultWait`1.Until[TResult](Func`2 condition)
at CyberArk.WebAutomationUtils.WebElementWrapper.WaitUntilElementIsNotVisible(Int32 actionTimeout)]
[02/10/2024 | 11:19:39] | :: | PSMDU019I Dispatcher trace message: [WebElementWrapper :: WaitUntilElementIsNotVisible -> END]
02-26-2026 01:34 AM
I got the Solution for issue WaitUntilElementIsNotVisible and that button does not disappear as per website funtionality
Go To platform configuration: Select platform > Go to Additional policy setting > Right Click parameter > and Add poarameter named as WaitUntilElementIsNotVisible > Set value in Second( keep as less you can ) For Ex : 1. Save.
Now Connector will for just 1 second WaitUntilElementIsNotVisible and if doesnot disappear it will mark that as error and move to next step.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

