Hi
We encounter same issue we have a application that cant be done becource the screen size is to low and many objects it not visible on it.
I have tryed alot of difrent ways to fix this and nothing helps. The set Screen Resolution is not working becource it cant set it when it does not have the size available.
My theory is becource it connects with RDP with the size setting 1024x768 it will be stuck here.
Take a look at the part of the log below
{"eventDataSchemaVersion":"1.0","schemaVersion":"1.0","agentClientId":"7Jx/Y9e+D7jCvHIYBu5komXLj6+Zr/Og","correlationId":"952f13df-0848-4bd8-a8db-a4d8da583ede","clientSessionId":"","clientRequestId":"","component":"UIFlowService","eventType":"NotSpecified","traceLevel":"Warning","operationName":"NamedPipeServer.ListenAsync","eventTimestamp":"2021-02-25T07:15:19.0798765Z","durationInMilliseconds":"-1","exception":"System.Threading.Tasks.TaskCanceledException: A task was canceled.\r\n at Microsoft.Flow.RPA.Common.RpcOverNamedPipes.NamedPipeBase.<ExecuteWithTimeoutAsync>d__35.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Microsoft.Flow.RPA.Common.RpcOverNamedPipes.NamedPipeServer.<ConnectPipeAsync>d__3.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Microsoft.Flow.RPA.Common.RpcOverNamedPipes.NamedPipeBase.<ConnectAsync>d__41.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Microsoft.Flow.RPA.Common.RpcOverNamedPipes.NamedPipeBase.<EnforceInitializationAsync>d__42.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at Microsoft.Flow.RPA.Common.RpcOverNamedPipes.NamedPipeBase.<ListenAsync>d__44.MoveNext()","message":"Failure while reading from Named Pipe 'NativeHost_447e7ad7-becf-4b28-ac3a-a24e1825a6d1' (isServerEnd 'True')","eventData":{"osInfo":{"name":"Microsoft Windows NT 6.2.9200.0","version":"Microsoft Windows 6.2.9200","architecture":"Win32NT"},"executionInfo":{"sessionId":0,"processName":"UIFlowService","threadId":4,"contextId":0},"machineInfo":{"screenResolution":"1024x768","processorCount":"4","netVersion":"4.0.30319.42000","windowsProductName":"Windows Server 2019 Standard"},"httpStatusCode":0,"agentVersion":"2.4.63.21036"},"roleInfo":{}}
The Gateway and Power Automate Desktop is up to date.
I have tryed on a non virtual Windows 10 PC this encouter same issue aswell.
Hope you can fix this maby with the option to set the Screen Resolution on the Gateway instead so it will connect with that on the RDP
