StudioWeb LocalWorkspace projects not working for some users- All Regions
Nov 19, 10:22 UTCNov 19, 16:10 UTC
Duration
5h 48m
Impact
Minor
Root cause
Not disclosed
UiPath, 90 days
59 incidents
Affected
Studio WebEuropean Union - Studio WebUnited States - Studio WebJapan - Studio WebAustralia - Studio WebSwitzerland - Studio WebUAE - Studio WebSouth Korea - Studio WebDelayed US - Studio Web
Final update
The issue is resolved, and Studio Web Local Workspace projects are working normally again. We apologize for the inconvenience.
Timeline
- Resolved · Nov 19, 16:10 UTC
The issue is resolved, and Studio Web Local Workspace projects are working normally again. We apologize for the inconvenience.
- Monitoring · Nov 19, 15:44 UTC
We have finished deploying the hotfix to all regions. We are monitoring to make sure the issue is fully resolved and will post another update when it is.
- Identified · Nov 19, 15:08 UTC
The hotfix has been deployed to the Community, Australia and Japan regions, and users in these regions are unblocked. Deployment to the remaining regions is in progress. We will post an update once it is complete.
- Identified · Nov 19, 14:07 UTC
A hotfix has been deployed and validated in the Community Environment. Users on Chrome version 158 will now see an in-app notice in Studio Web with an option to clear the Local Workspace solutions list. After clearing it, users can create new solutions and open existing solutions from disk again. Rollout of this hotfix to the remaining regions is in progress, and a permanent fix is being worked on. Until the hotfix reaches your region, users can continue to use the workaround We will post another update within the next hour
- Identified · Nov 19, 13:03 UTC
We are continuing to roll out the hotfix to mitigate the issue for users on Chrome version 158. Users can continue to use the workaround: remove the Local Workspace solutions from the recent list one at a time using More → Remove from recent, then create new solutions and re-import any previously exported solutions. We will post another update within the next hour.
- Identified · Nov 19, 11:45 UTC
identified cause: Chrome version 158 changed how browser folder permissions work, so permissions previously granted to solutions in the 'Local Workspace' are no longer recognized. As a result, users on Chrome 158 cannot open existing Local Workspace solutions. We are currently rolling out few hotfixs to mitigate the issue. Workaround: remove the Local Workspace solutions from the recent list one at a time, using More → Remove from recent. After that, you can create new solutions and re-import any solutions you exported earlier. We will post another update in next 1 hour.
- Identified · Nov 19, 10:57 UTC
Chrome users who upgraded to version 158 are unable to access recent Local Workspace projects in Studio Web. Existing solutions cannot be opened, and new solutions cannot be created. We have identified the issue and are working on a hotfix. Workaround: Remove the Local Workspace solutions from the recent list one by one by selecting More → Remove from recent. Once all solutions have been removed, users can create new solutions and re-import previously exported solutions.
- Investigating · Nov 19, 10:22 UTC
Some users might not be able to access projects in the 'Local Workspace' in StudioWeb. Existing projects might fail to open, and new projects cannot be created. Issue is limited to few users only
More from UiPath
Full historySome users are experiencing issues when creating new Integration Service connectionslasted 2h 36mSign-in and authentication failures in Automation Cloud - All regionslasted 51mEurope Region – DataService (Fabric) is experiencing increased latency and intermittent failureslasted 49mUnited States - Notification Service - Degradedlasted 8h 9mMultiple Regions – Serverless Robots – Jobs using Microsoft 365 activities failinglasted 15h 12mMultiple Regions - Communications Mining - Delayed email synclasted 28h 32m