'Switch to a new window in a browser session' - 'Unsuccessful vs ITC'?

Mitch Dale

Hey @Product,

I have a web RPA WF that has numerous 'Switch to a new window in a browser session' WAs because the website my WF interacts with always opens things in new tabs instead of in the same tab.

This has only happened once so far, but I had a WF run where the user was logged out of the system. Thus, when the WF came to a 'Switch to a new window in a browser session', the tab that the WF was to switch focus to wasn't actually there. The job as a result ended with an ITC:

https://portal.skillpack.io/wrkstation/97733db5-b6e0-4c94-9f09-8b5de46eb065

Is there any particular reason that this job ends in an ITC if the window/tab that the job is searching for wasn't found? It seems more apt to have this outcome be an 'Unsuccessful' path instead. The main issue that this presents for me is I can't have any error handling branch in my WF (e.g. re-log in); the WF just stops unbeknownst to me unless I check on it.

Dylan

Mitch Dale I think you might have shared the wrong job here. My reports say this is a Click element on a website job that completed successfully.

Mitch Dale

@Dylan my bad

This is the failed job I meant to share:

d86e2d72-2deb-4ca2-b065-7a944387ecd6

Dylan

Mitch Dale Thanks, I agree it would be nicer for this to return unsuccessful so users can perform thier error handling. I have created a ticket here: https://wrk-technologies.atlassian.net/browse/SUP-1717

Dylan

@[deleted] An update to the Wrk Action has been deployed. It will now return 'Unsuccessful' instead of ITCing when it can not find the window searched for.