All workflows in my Logic App that use Inline Code stopped working

Question

All workflows in my Logic App that use Inline Code stopped working

Igbeka, Emeka 5

I've had workflows within my Logic App working perfectly fine until yesterday. Whenever they are triggered, they remain in a perpetual running state until I cancel them. They all get stuck at the Inline Code section.

Note

This has been working perfectly fine for the last 3 months.
I tested it with the default "Hello World" and it didn't work so it's not my script/code
I also made the configuration change and updated the FUNCTIONS_EXTENSION_VERSION to 4.837.1.23604

Screenshot 2025-08-27 152232.png

0 comments

1 answer

Your answer

Answer 1

Suwarna S Kale 4,526 Volunteer Moderator

Hello Igbeka, Emeka,

Thank you for posting your question in the Microsoft Q&A forum.

A sudden failure of previously operational Logic App workflows, particularly within Inline Code operations, indicates a platform-level runtime disruption rather than a code defect. The issue almost certainly stems from Azure's deprecation of the underlying Node.js version that powered the Functions runtime. Your Logic App's configuration was likely dependent on a now-retired version, such as Node.js 14 or 16, causing the initialization process to hang indefinitely.

The solution requires explicitly overriding the default platform setting by defining a new application configuration, WEBSITE_NODE_DEFAULT_VERSION, with a value of ~18 to mandate the use of a current, supported Long-Term Support version. This forces the runtime onto a stable and compatible foundation, resolving the initialization failure. Consequently, the Inline Code action can then execute successfully, allowing your workflows to proceed to completion without further interruption.

Please, let me know the response helps answer your question? If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. 🙂

Igbeka, Emeka 5 Reputation points

2025-08-28T17:26:29.41+00:00

My WEBSITE_NODE_DEFAULT_VERSION was already set to ~20.
I made the update, and it didn't make any difference.
Pashikanti Kumar 1,725 Reputation points Microsoft External Staff Moderator

2025-08-29T05:22:03.0266667+00:00

Hi Igbeka, Emeka,

To restore functionality for Logic App Inline Code

Key: WEBSITE_NODE_DEFAULT_VERSION

Value: ~18 (recommended)

Save the changes and restart your Logic App.

This update ensures compatibility with the supported Node.js runtime and resolves the issue where workflows hang at the Inline Code step.
Igbeka, Emeka 5 Reputation points

2025-08-30T22:17:45.7366667+00:00
Hi Pashikanti,

Making this change did not fix the issue. For your understanding, these are my current settings:

FUNCTIONS_EXTENSION_VERSION: ~4

FUNCTIONS_INPROC_NET8_ENABLED: 1

FUNCTIONS_WORKER_RUNTIME: dotnet

WEBSITE_NODE_DEFAULT_VERSION: ~18

Additionally, when I updated the NODE version, I got a notification in the overview section informing me to upgrade my logic app to a newer version as Node.js 18 LTS has reached EOL.
Pashikanti Kumar 1,725 Reputation points Microsoft External Staff Moderator

2025-08-31T16:49:43.14+00:00
Hi Igbeka, Emeka,

Thank you for sharing your settings and the notification you saw about Node.js 18 reaching End of Life. Here’s why your Logic App workflows with Inline Code are stuck and how to fix the problem:

Node.js 18 LTS is now End of Life. This means Microsoft is phasing out support for it in Logic Apps, and the runtime required to run your Inline JavaScript code is no longer available.

You’re using a newer .NET 8 setup, but Inline JavaScript code in Logic Apps relies on Node.js, so it isn’t working anymore, even if your overall Logic App is set to .NET.

To Mitigate the issue

1. Move Your Inline Code to C# (Recommended Approach)

Microsoft now supports C# Inline Code actions that work with .NET 8, and this does not depend on Node.js. This is the future-proof way, and it will keep your workflows running without interruptions:

Replace your JavaScript Inline Code steps: Open your Logic App workflows, remove the "Execute JavaScript Code" actions, and add the new "Execute CSharp Script Code" action instead.

Convert your JavaScript code to C#:

For example, if your JavaScript code looked like this: return workflowContext.trigger.outputs.body.message + " - processed"; You’d write this in C#: public static string Run(string message) {     return message + " - processed"; }

You can use the new C# Inline Code action for all your workflow scripting needs, and it runs perfectly on .NET 8 (no need for Node.js).

2. Update Your Node.js Setting (Temporary Workaround)

While you’re migrating to C#, update your Node.js setting:

Set WEBSITE_NODE_DEFAULT_VERSION to ~20 instead of ~18. This tells Azure to use the newest Node version that’s still supported if any functionality still relies on it.

3. Double-Check Your Other Settings

Your settings should look like this:

Shell

textFUNCTIONS_EXTENSION_VERSION: ~4FUNCTIONS_INPROC_NET8_ENABLED: 1FUNCTIONS_WORKER_RUNTIME: dotnetWEBSITE_NODE_DEFAULT_VERSION: ~20

This supports the modern .NET and the newest Node.js available for temporary compatibility.

Please note:

Azure Logic Apps is beginning to retire JavaScript-based inline code support in favor of the more powerful and future-ready C# inline scripting. This means converting your Logic App scripts to C# will keep your solutions supported and running smoothly going forward.

csharppublic static string Run(string message){    return message + " - processed";}

javascriptreturn workflowContext.trigger.outputs.body.message + " - processed";

Reference Documents:

How to upgrade and use C# inline scripting: Upgrading Logic Apps Standard to .NET 8

How to use Inline C# Code in Logic Apps: Announcement: .NET C# Inline Action for Azure Logic Apps

Create and run .NET code in workflows: Create and Run .NET Code from Workflows Thank you for sharing your settings and the notification you saw about Node.js 18 reaching End of Life. Here’s why your Logic App workflows with Inline Code are stuck and how to fix the problem:

Node.js 18 LTS is now End of Life. This means Microsoft is phasing out support for it in Logic Apps, and the runtime required to run your Inline JavaScript code is no longer available.

You’re using a newer .NET 8 setup, but Inline JavaScript code in Logic Apps relies on Node.js, so it isn’t working anymore, even if your overall Logic App is set to .NET. To Mitigate the issue 1. Move Your Inline Code to C# (Recommended Approach) Microsoft now supports C# Inline Code actions that work with .NET 8, and this does not depend on Node.js. This is the future-proof way, and it will keep your workflows running without interruptions:

Replace your JavaScript Inline Code steps:
Open your Logic App workflows, remove the "Execute JavaScript Code" actions, and add the new "Execute CSharp Script Code" action instead.

Convert your JavaScript code to C#:

For example, if your JavaScript code looked like this:
return workflowContext.trigger.outputs.body.message + " - processed";
You’d write this in C#:
public static string Run(string message)
{
    return message + " - processed";
}

You can use the new C# Inline Code action for all your workflow scripting needs, and it runs perfectly on .NET 8 (no need for Node.js). 2. Update Your Node.js Setting (Temporary Workaround) While you’re migrating to C#, update your Node.js setting:

Set WEBSITE_NODE_DEFAULT_VERSION to ~20 instead of ~18.
This tells Azure to use the newest Node version that’s still supported if any functionality still relies on it. 3. Double-Check Your Other Settings Your settings should look like this: Shell textFUNCTIONS_EXTENSION_VERSION: ~4FUNCTIONS_INPROC_NET8_ENABLED: 1FUNCTIONS_WORKER_RUNTIME: dotnetWEBSITE_NODE_DEFAULT_VERSION: ~20 This supports the modern .NET and the newest Node.js available for temporary compatibility. Please note: Azure Logic Apps is beginning to retire JavaScript-based inline code support in favor of the more powerful and future-ready C# inline scripting. This means converting your Logic App scripts to C# will keep your solutions supported and running smoothly going forward. csharppublic static string Run(string message){    return message + " - processed";} javascriptreturn workflowContext.trigger.outputs.body.message + " - processed";

Reference Documents:

How to upgrade and use C# inline scripting:
Upgrading Logic Apps Standard to .NET 8

How to use Inline C# Code in Logic Apps:
Announcement: .NET C# Inline Action for Azure Logic Apps

Create and run .NET code in workflows:
Create and Run .NET Code from Workflows

Share via

All workflows in my Logic App that use Inline Code stopped working

1 answer

Your answer