Desktop Targeting - Screenshots
AnsweredHello everyone,
Recently I have stumbled upon a new issue where Foxtrot wouldn't target Desktop properly on different accounts.
I have a robot set up, that was supposed to take a screenshot of the desktop in case unexpected error happened. It was working fine until recently, where now it can only target desktop on the account the action is created. If I create a step to take screenshot by targeting desktop it will work without issues on account 'A', however if I start the robot from account 'B' the step will fail and when opened in edit mode it will say that the target couldn't be found.
Did anyone experience this and know the cause and how to fix it?
Robot is created and run on: Windows Server 2016 Ver 1607, Foxtrot ver 14.6.2
Regards,
Andrius
-
Official comment
Hi Andrius,
The cause of this issue is that the Windows desktop can actually be in two different modes. So, when you have made the action with Foxtrot, the desktop will have been in one of the two modes. But, at some point, it will likely be in the second mode, causing the "Target Not Found". The solution to the problem is that when you experience a "Target Not Found", you perform a new drag-and-drop to the desktop and create first an "If"-statement with "if the target is found" (make sure to make an "Else"), then put the old action in the else clause and a new screenshot action for the desktop in the if clause.
I hope this makes sense, I know it is a little cryptic, but I think it's best not to begin to try to explain why the desktop has two different modes, then it really starts to get confusing.
Comment actions -
Hi Tatyana
The resolutions were different. However I just made another test, where logged in to the server using the same connection settings with each user and got the same issue. I created screenshot step with user A, closed the connection, then connected with user B using the same connection settings, to the same server, and it couldn't detect the desktop anymore.
I have also tried connecting back to user A with different resolution settings and it had no issues detecting larger desktop.
Please sign in to leave a comment.
Comments
4 comments