CRITICAL Regression: Coded Workflows completely broken (Compiler AND Runtime crashes)

Help Studio
1

Hi,
unless I have somehow fundamentally misconfigured my environment, this is the most critical regression I have witnessed in years. This update has effectively bricked my entire Coded Workflow implementations.

Everything worked perfectly two weeks ago. After updating UiPath Studio twice (currently on version 2026.0.182 LTS), the feature is now unusable.

Here is an example of completely valid, trivial C# code:

using System;
using System.Threading.Tasks;
using UiPath.CodedWorkflows;

namespace Testing
{
    public class Test : CodedWorkflow
    {
        [Workflow]
        public async Task Execute()
        {
            await Task.Delay(1000);
            Console.WriteLine("Test");
        }
    }
}

Issue 1: The Code Generator produces broken C#
For the code above, I am getting 8 Compilation Errors. Why? Because your source code generator is producing syntactically invalid wrapper code in the .local folder. How did this pass QA?

image
image974Ă—132 68.3 KB

After looking into the generated code, I found the following:

  1. Missing Generic Type Argument (CS1031): The generator creates properties like public OutArgument<> Output without specifying a type inside the angle brackets.
  2. Invalid Cast Syntax (CS1525): The generator produces Output.Set(endContext, ()result["Output"]); with empty parentheses, resulting in an invalid cast expression.
  3. Invalid Void Assignment (CS0029): The generated ExecuteAsync method attempts to assign the result of a Task (void) method to a variable (var result = await codedWorkflow.Execute()), which is illegal in C#.

Issue 2: The Runtime crashes on await I was forced to “fix” your generator’s mess by changing my method signature from Task to Task<string> just to get it to compile. But it gets worse. Even if I bypass the compiler errors, the runtime execution engine is broken.

Running this code:

[Workflow]
    public async Task<string> Execute()
    {
        await Task.Delay(1000); // CRASH
        return string.Empty;
    }

Results in a NullReferenceException immediately after the await.
No image of the errors because this is my first (and last) post.

This indicates that the execution engine is losing the synchronization context during async operations, causing the internal EndExecute handler to crash upon return.

Summary:

  1. I cannot compile standard void workflows because the generator is broken.
  2. I cannot run async workflows because the runtime crashes on await.
1 Like
Forum Engagement Daily Reports
2

Hi @Niklasd,
This is a confirmed regression in recent UiPath Studio versions affecting Coded Workflows. The source generator produces invalid C# and async workflows crash at runtime after await. It is not an environment issue. There is no workaround in 2026.x other than downgrading to a previously stable Studio version or avoiding coded workflows and async until UiPath releases a fix. Open a critical support ticket and pause upgrades.

Thanks and cheers

3

Are you using enterprise version? This looks like community version which is not for the production purpose.

4

Hi, @Niklasd !

Thanks for reaching out. We are aware of this regression, the fix has already been introduced in 25.10.3 version and will also come with the 2026.0.183.

1 Like
5

Hi @Gabriela_Vaduva,
thanks for the answer. When do you think the new update for the community version will be released? Will it happen this year?

6

hi @Niklasd !
yes, we are in the process of releasing a new version today or at the beginning of the next week. I’ll update on here once the new version is available.
thanks!

1 Like