Perform a Mouse Action Click not Opening Menu

Leeann

Hey @Product ,
I'm noticing the Perform a mouse action on a website WA will click the element and trigger the dropdown successfully when initiated from the Test Panel
Execution ID: 7d59a800-d05a-4d58-a957-d8ea29de43fc

But in the actual run, it'll return success without the dropdown being made visible.
Execution ID: 2be60f21-e772-4b43-b15c-872eaa482abc

The same thing is happening when we use the vision WA
Execution ID: ca33b5b2-7ff3-4b9b-b894-b5668fb0b1c6

When monitoring the live run, the bot will click the element, return success, but the dropdown doesn't appear.

WA: https://account.wrk.com/designer/?wrkflow_id=58116&client_id=5818&canvas_search_keyword=e588779c-b39e-4c21-ad4c-ca9a4c0b3805

When the job is reset it works.
And sometimes when monitoring the run, right before the css click it'll scroll up and down a lot before reporting unsuccessful. I'll try to capture a recording on the next run

Let me know if there's something else I can do to fix this

Nick

@Leeann Can you please try adding a delay to your Wrkflow? Feels like the click might be happening before everything has successfully loaded on the site. This should be taken care of automatically but this site might be an exception.

Leeann

Hey Nick
I've added a delay but neither WA is clicking the element.
I've also recorded the scrolling action it does instead of clicking.
https://drive.google.com/file/d/1PcTaTfmkbk5ZY7sZGbG_pPjc15_fUeT9/view?usp=sharing

Launch: https://account.wrk.com/v2/dashboard?client_id=5818&wrkflow=58174&panel=launches&launch=1439952
Execution ID: e29bf343-9361-431a-a463-427a4dfe2cd4
Execution ID: 97d0bdd0-dc73-418b-a10c-1d582b1fdb71

WA deep link: https://account.wrk.com/designer/?wrkflow_id=58174&client_id=5818&canvas_search_keyword=a93f0807-b974-4185-8d00-d7a1627836a0

Dean

@Nick as you are going through the tickets - this has been failing all week and is blocking this WF

Nick

Issue:

After the work order is updated there is a "no matches found" box in the top left corner that shows up. It's small and feels unimportant but it's actually masking the entire application for some reason so the rest of the DOM can't be interacted with. Seems to go away if you click on the screen though. You can likely fix this whole thing by adding a simple click in a place that dismisses the message but is sure not to navigate anywehre else (like the black space on the header).

I have to leave now but I'll try it first thing in the morning if you don't beat me to it.

General Wrfklow thoughts:

Why are we logging in each time? Browser State works for Appfolio
Why are we looping through a bunch of old items each time? Feels wasteful, could we bulk filter these out instead of 1 by 1?

bug:
Looks like Check if element is visible still takes 30 seconds even if set to 0. This is super annoying. I'll make a ticket.

Leeann

Hey Nick

To answer the questions:

Nick Why are we logging in each time?
It doesn't login each time, it launches the login flow which checks if the dashboard is visible and is used by other wrkflows to streamline updating the login process when Appfolio makes an update (i.e the new Unified Login).
If the dashboard is visible, the wrkflow ends, if not it logs in.

Nick Why are we looping through a bunch of old items each time?
The downloaded Appfolio report doesn't track which properties Wrk has processed.
If the property has been processed it logs a message for visibility on why it was skipped and moves onto the next.
The branching step is for an expansion in which the automation would follow up on processed properties 2 days after Wrk sent follow-ups.

Thank you for catching the the no matches found issue. I didn't notice it until now.

I've attached the image for quick reference in the future.

Thank you