Hello Community,
Why does my Community license Studio Web is taking so much time load a empty project and manual trigger is not available in the triggers after opened do i need to do any changes or all are facing this issue
@loginerror Kindly help me out here or redirect this to a person who might help me on this . Whenever i open the studio web project it straight away asks me to select the trigger and there is no option of manual trigger there
I tried updating the studio still i have the issue
Thank you for reporting this issue. To help us investigate further, could you please share a bit more information?
Does this happen with every new RPA project you create?
Could you share the URL shown in your browser when you open the project?
Are there any network restrictions on your machine that might prevent a NuGet restore?
Additionally, sharing a short video recording of the behavior would be very helpful.
NO restrictions , im using my personal lap and using community license
Here is the video whole video is 7 mins almost 6 minutes it is loading to open a new project
@Sudharsan_Ka In order to investigate this issue further, we need some logs from your machine. Could you please archive the log files from the %localappdata%\UiPath\Logs folder and send them to me? Thanks!
Thanks for sharing the logs. I went through the logs from Sept 4 and 5 and found the cause of the NuGet errors.
The errors are not caused by missing packages or by a problem with the feed. They are the result of a network issue on the machine. Every single package failure in the logs has the same underlying exception:
One error is “The SSL connection could not be established, see inner exception. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.”
In other words, the HTTPS connection to the package feed (pkgs.dev.azure.com) is being cut off during the TLS handshake. The same thing happens to api.nuget.org, where responses “ended prematurely”.
The failures are intermittent. A number of downloads did go through, including a 48 MB package, so the feed itself is reachable. Something in between is resetting some of the connections.
Likely cause
“Connection forcibly closed by the remote host” during the SSL handshake is the typical signature of a TLS-inspecting proxy, firewall, VPN, or endpoint security product interfering with HTTPS traffic.
What to check
Is the machine on a corporate VPN, or behind a proxy or web security product (for example Zscaler, Netskope, or an antivirus with HTTPS scanning)?
As a quick test, open the same project from a different network, for example a mobile hotspot. If the errors disappear, the network is confirmed as the cause.
Ask your IT team to allow, or exclude from SSL inspection, the following hosts: