Hello,
Thank you for reaching out regarding this matter.
I saw your second post in the Devolutions Cloud section of the forum. I will remove it so we can continue using this topic moving forward.
From my understanding, the behavior you described is already known by the development team. Workspace currently uses a two-step authentication process: first, authentication to the Devolutions Account to select a Devolutions Cloud instance, and second, authentication directly to the selected Devolutions Cloud.
The team is currently investigating a better approach, as the current setup can lead to the issue you are experiencing. As a workaround, they suggested configuring the Devolutions Cloud URL directly in the Workspace extension settings before attempting to connect to it.
Could you please test this workaround and let me know whether it resolves the issue on your side?
Also, please let me know if this aligns with your use case. Otherwise, feel free to share additional details about your setup and workflow so we can better understand the situation.
I look forward to your reply.
Best regards,
Special Q&A