[UiPath Studio Community] Debug works a few times, then suddenly fails with "invoked workflows are missing" – Error code 7

[C_ng_Nguy_n_Ng_c (Cương Nguyễn Ngọc)]

Description:

I’m using UiPath Studio Community on Windows 11, with a REFramework project.

When I debug, the first few runs work fine, but then it suddenly fails to build and I can’t debug anymore. I have not deleted or moved any files manually.

Error message:

[Error] The following invoked workflows are missing:
[Error] Project build failed. Error code: 7.

Studio reports that the following .xaml files cannot be found:

Missing file	Called from
Performer/verify_and_create_new_customer.xaml	Framework/Process.xaml
Performer/get_job_name.xaml	Framework/Process.xaml
Performer/create_new_job_code_if_needed.xaml	Framework/Process.xaml
Framework/InitAllSettings.xaml	Tests/ProcessTestCase.xaml
Framework/InitAllApplications.xaml	Tests/ProcessTestCase.xaml
Framework/GetTransactionData.xaml	Tests/ProcessTestCase.xaml
Framework/CloseAllApplications.xaml	Tests/ProcessTestCase.xaml

---

What makes this strange: The files still exist on disk (I verified in File Explorer), but Studio reports them as missing. Also, the error does not happen immediately — it only appears after successfully debugging a few times first.

What I’ve already tried:

• Restarted UiPath Studio → still the same error
• Uninstalled and reinstalled UiPath Studio Community → still the same error
• Copied all the code into a brand new project → still the same error

None of the above worked. The error keeps coming back after a few successful debug runs.

Questions:

1. Why does Studio report files as missing when they still exist on disk?
2. Could this be a Studio cache corruption issue that occurs after a few debug runs?
3. Is there a permanent fix, rather than just a temporary workaround?

[yedukondaluaregala (YK)]

@C_ng_Nguy_n_Ng_c Welcome to community!

Remove the invoke workflows activities and update the system activities package.

Then add the invoke workflow activities again and call those respective workflows in all mentioned places.

Try and Let me know if this works.

Happy Automation

[Prashanth_D (Prashanth_dharavath)]

Hi @C_ng_Nguy_n_Ng_c,

1. Check for Broken Relative Paths in XAML Invokes
   For each Invoked Workflow File activity:

• Remove the workflow/activity.
• Update all the packages to stable version.
• Browse and reselect the target XAML.
• Save all files.

2. Windows path length issues can cause intermittent build failures.
   Try moving the project closer to the root: Example: C:\RPA\TestProject
   instead of: C:\Users<user>\Documents\Projects\REFramework...

3. Delete All Temporary Project Artifacts

• Close Studio and remove: .local, .objects, .bin, .obj etc.
• Then reopen Studio and restore dependencies.
• Also clear:
  %localappdata%\UiPath
  %localappdata%\UiPath.cache
  %localappdata%\UiPath\Logs

4. Check for Case-Sensitivity Mismatches
   Even on Windows, Studio sometimes becomes sensitive to path casing when references are serialized.
   For example: Performer/Get_Job_Name.xaml vs Performer/get_job_name.xaml

Try the above steps and see if any one of them resolves your issue.

Thanks!

[gorby (RPA Ninja)]

Hi, Vietnamese @C_ng_Nguy_n_Ng_c

As others have pointed out, the most likely cause is an outdated version of the UiPath.System package.
Please try updating the UiPath.System package and restart your UiPath.

May Ngọc Hoàng Thượng Đế bless you!

[Anil_G (Anil Gorthi)]

@C_ng_Nguy_n_Ng_c

One strange thing I see is your workflows are deeply nested inside folders why is that?

are you opening the project from nupkg directly downloaded from orchestrator?

cheers

[Italo_Cosendey (Ítalo Cosendey)]

I’m having the same problem. This happened after a UiPath update. All packages are properly updated. Has anyone managed to solve it?

[C_ng_Nguy_n_Ng_c (Cương Nguyễn Ngọc)]

thank you. it worked

[C_ng_Nguy_n_Ng_c (Cương Nguyễn Ngọc)]

I followed your instructions, but every time I update a package (any package), it debugs successfully once, then the next time it fails with the same error again.

[achr (Aris Christoforou)]

I face the same issue after the last Studio update (Studio 2026.0.196-cloud.23786 - 6/23/2026)

[Tudor_Mircea_Comandaru]

I reproduced the same issue in a blank Windows project and found a consistent workaround.

It appears to be related to Invoke Workflow File path resolution when the invoked XAML file is located inside a project subfolder.

Bug 1 — Existing invoked workflow is reported as missing

Steps:

1. Create a new blank Windows project.
2. Create a subfolder, for example Folder.
3. Add a workflow inside that folder, for example test.xaml.
4. Invoke it from Main.xaml using Invoke Workflow File.

The XAML contains a valid relative path:

WorkflowFileName="Folder\test.xaml"

The file exists physically at:

<ProjectRoot>\Folder\test.xaml

However, Studio can fail the build with:

The following invoked workflows are missing:
<ProjectRoot>\Folder\test.xaml

Project build failed. Error code: 7.

The file is not actually missing.

Workaround:

If I move the same test.xaml file from the subfolder to the project root and change the invoke to:

WorkflowFileName="test.xaml"

the project builds successfully.

Bug 2 — Duplicate generated class with double backslash path

In a blank project, when dragging and dropping a workflow from a subfolder into Main.xaml, Studio can generate/display the path with escaped/double backslashes, for example:

Folder\\test.xaml

When building/debugging, this can fail with a duplicate generated class error, where the same workflow seems to be resolved twice after path normalization, for example:

Following files would result in same class name within the same namespace:
Class='BlankProcess.Folder.test'
Files='<ProjectRoot>\Folder\test.xaml, <ProjectRoot>\Folder\test.xaml'

So there seem to be two related symptoms:

1. With subfolder paths like Folder\test.xaml, Studio may report an existing invoked workflow as missing.
2. With escaped/double backslash paths like Folder\\test.xaml, Studio may resolve the same workflow twice and fail with duplicate generated class errors.

This does not look like a missing file, cache, REFramework, or corrupted project issue. It looks like a regression in the Studio compiler / Invoke Workflow File path resolver when using subfolders after the latest Studio update.

Environment:
Studio 2026.0.196-cloud.23786
Windows project

[alex.huang]

same problem XD Have you found a solution yet?

[mcuciur (Marius Cuciureanu)]

When debugging projects, Studio compiles each workflow into a separate assembly. This way, it doesn’t have to recompile the entire project when you change a single file.

There are two known issues in the latest release, both related to the Invoke Workflow File activity:

1. Cache mechanism error (the one you encountered)
   Workaround: Use the Remove project cache option, which clears the cache portion of the .local folder. Alternatively, you can delete the .local folder manually.

2. Duplicate namespaces/classes
   This happens when the path in the Invoke Workflow File activity contains an extra \ , which confuses the compiler.
   Workaround: Remove the extra \ from the path.

I understand these 2 will be fixed asap.

[mcuciur (Marius Cuciureanu)]

Is the problem solved after the latest update?

[ae.nz.testing]

Hello, I’m having the same issue, I tried everything, the packages are updated:

The files are in the right folder:

After each process start I erase the cache, I keep updating the Invoke Workflow files.

After doing all that it only allows me to run it just once, then again the error shows up.

[mcuciur (Marius Cuciureanu)]

What Studio version are you using?

[ae.nz.testing]

Hi, I’m using version Studio 2026.0.196 STS - Community.