Question
Hoverstate
US
Last activity: 9 Mar 2021 8:54 EST
automation always hangs on waitforcreate after multiple successful loops
As title - I have an automation which loops through several forms and uses a waitforcreate to know when the form is loaded and to enter details. It works through several loops but hangs after 5-10 passes. It does not exit the false leg, as if it timed out failing to match, it simply hangs for 10+ minutes on that screen.
Here are surrounding logs, 410-01 line is immediately before the waitforcreate
Any suggestions why this may be happening?
Ford Motor Company
US
We have faced similar issue and opened an SR with Pega. Pasted the solution:
SR-D64104: RPA Process Hanging While getting the Next Claim
Perform the following local-change: Replace PerformClick method with RaiseEvents(onclick)
Pegasystems Inc.
US
@DanQuinlogGiven that your log ends with a WaitForCreate, we'd really need to see what happens after some time has passed after you have clicked the button and started waiting. I would suggest opening a support request as they'd be able to assist you one-on-one (virtually of course).
If that is not an option for you, you should look at the element you are clicking on rather than the wait for create. I would be curious if the WFC never returned as that would indicate something is frozen in Runtime (i.e. you really shouldn't see anything being logged at that point). You could try clicking that element differently as the previous commenter noted, or you can examine your threading and possibly use a Parallel Process to click on one thread and wait on another.
Updated: 5 Mar 2021 16:37 EST
Hoverstate
US
Unfortunately there isn't an onclick event to raise for this button. Sendkeys works while I'm watching the vm but when I log out it fails. Maybe that's a locked screen issue like you mentioned here.
https://collaborate.pega.com/question/unable-take-screenshot-unattended-rpa
Pegasystems Inc.
US
@DanQuinlog Yes, very likely. SendKeys doesn't work on a locked screen as it is literally mimicking what you'd do if you were on the machine. I would suggest you open a support case and someone can assist you and take a look at your logs and solution.
Pegasystems Inc.
US
@DanQuinlogIn looking at your log, I think your problem is that you are calling Rematch. I would not call Rematch if you can avoid it. That used to have a potential for causing a hang if it were called during matching (I am not sure if it still does, but this sure seems like the same issue). It should be used sparingly if at all and not on every iteration. Perhaps look at your match rules to see if you can get your controls to match with a rematch, or look to see if there is some other property of the page you can check to see if a rematch is even necessary. Perhaps your error message appears inside a DIV that you can get the InnerText from to see if the error is present. Perhaps there is some other event that fires when the error message is present that you can use.
Updated: 9 Mar 2021 8:47 EST
Hoverstate
US
@ThomasSasnettThank you, I will review that. I'm still new to pega so any best practices recommendations are welcome.
Right now I found I was able to get through the iterations by closing IE completely and reopening every so many loops, but while that works it isn't pretty so I'm still working on it. I'll let you know if working out any rematches can solve this ^_^,b
Pegasystems Inc.
US
@DanQuinlog Make sure you perform the same steps in interrogation. Go through several times and if you ever need to use Refresh Matching there, you can examine what was matched before and what is currently matched to see if there are tweaks you can make.