If you're getting vague compile errors like a bare Error code 1, or a project runs on one PC and won't open cleanly on another, check where the project folder lives. If it's inside OneDrive or any always-sync cloud folder, that's very likely your problem.
The mistake
Putting the live Studio project folder inside OneDrive (or Dropbox, or any folder that syncs all the time) so you can "share" it between machines. It feels convenient. It isn't.
Why it bites
Studio writes a lot of files while you work: project.json, generated files, and a local cache in the hidden .local folder. A sync client can lock those files, leave some of them online-only, or still be downloading subfolders when Studio tries to compile.
On the forum that usually shows up as a bare Error code 1, or a project that works on PC1 and won't open on PC2 until someone copies it out of OneDrive. Network and shared drives cause the same kind of pain. Copy the project to a real local disk and it suddenly works.
The fix
1. Keep the working project on a local path.
Studio's default location is:
%USERPROFILE%\Documents\UiPath
But watch out: if Windows has redirected Documents into OneDrive, that default is a synced folder too. In that case put your projects somewhere that isn't synced, for example:
C:\UiPathProjects\
2. Share and version with Git, not by syncing the live folder.
In Studio, go to the Team tab and use GIT Init to add the project to a local Git repository, commit, then push to a remote. TFS and SVN are also supported if that's what your team uses. Studio leaves the .local folder out of source control by default, so your machine cache stays off the repo.
3. Need a cloud copy just for backup?
Zip or copy the project after you close Studio. Just don't develop inside the synced folder.
4. Don't confuse this with Sync to Cloud.
Studio's Sync to Cloud option syncs your project with Studio Web in Automation Cloud. It has nothing to do with OneDrive.
Quick check
Open File Explorer on your project path. If you see OneDrive sync icons on project.json or your workflow files, move the project to a local folder before your next publish.
Docs
- About automation projects (default location,
.local, Sync to Cloud): https://docs.uipath.com/studio/standalone/latest/user-guide/about-automation-projects - Adding a project to Git: https://docs.uipath.com/studio/standalone/latest/user-guide/adding-a-project-to-git
- About version control: https://docs.uipath.com/studio/standalone/latest/user-guide/about-version-control
Had a sync folder bite you? Tell me about it in the original forum thread, that's where the discussion is: https://forum.uipath.com/t/uipath-pitfall-of-the-week-2-keeping-your-studio-project-in-a-onedrive-sync-folder/5783803
Originally posted on the UiPath Forum: https://forum.uipath.com/t/uipath-pitfall-of-the-week-2-keeping-your-studio-project-in-a-onedrive-sync-folder/5783803
I post short UiPath fix videos from real forum questions on my YouTube channel, RPA Simplified.
Top comments (0)