The issue is, every time I try to run an unattended flow on my virtual machine it doesn't work, it gets triggered on the cloud platform, connectors work, and the flows are made correctly, but the desktop flow is sent to the queue, and it won't run, even if there are no other flows running. I can resolve the issue once I log in manually on the virtual machine and log in to PAD. After that it works for some time, and flows are running, but when I try to run in the next day it happens again. When I try to turn on PAD the next day I get an error, you can see it on the picture below. And that is a loop that happens every day, it can be solved but I need the flow to run 24/7, even after working hours when there isn't anybody to refresh the connection.
My guess is that there is something to do with the length of the session that is set somewhere or that there is some sort of restriction that is maybe causing these issues. Or maybe some sort of restriction that is used as a DLP policy for security reasons, in order to protect the company data. What can I ask my network admins to check or edit?

Report
All responses (
Answers (