C# Inline Scripting doesn't work anymore when custom functions are used

Question

C# Inline Scripting doesn't work anymore when custom functions are used

Griet Van Compernolle 0

I have a Logic App workflow which contains a C# Inline Script action, which runs without any issue:

Adding another workflow to the same Logic App making use of custom actions, my workflows with C# Inline Scripting don't work anymore.

User's image

As soon I remove the custom function from the lib-folder, my workflow with C# Inline Scripting works again.

It seems there is a conflict when the Logic App contains both C# Inline Scripting & custom functions.

We can consider to recreate the inline scripting as a custom function, but on the other hand we want to keep the current inline scripting and also use the custom function in one logic app.

Has anyone a clarification on this?

Praveen Kumar Gudipudi 1,495 Reputation points Microsoft External Staff Moderator

2025-11-10T17:15:14.99+00:00

Hello Griet Van Compernolle,

Are you calling C# Inline Script action logic app from custom actions logic app?
Griet Van Compernolle 0 Reputation points

2025-11-10T19:40:33.42+00:00
I have one logic app with 2 workflows:

1 workflow contains a local function action (https://learn.microsoft.com/en-us/azure/logic-apps/create-run-custom-code-functions).

1 workflow contains a C# inline script action

Both actions are separate, and doesn't call each other.
Praveen Kumar Gudipudi 1,495 Reputation points Microsoft External Staff Moderator

2025-11-11T17:19:47.8433333+00:00

Hello Griet Van Compernolle,

This is a known issue when mixing the two scripting types in one Logic App (especially in Standard tier). Microsoft’s documentation notes that “Inline Code and Custom Code actions should not be mixed within the same Logic App.

You have a few options:

Split into separate Logic Apps

Create two separate Logic Apps:

One for your Local Function action

Another for your Inline C# action

This completely isolates the runtimes, preventing version conflicts.
Griet Van Compernolle 0 Reputation points

2025-11-11T17:37:08.0166667+00:00

I've checked the documentation but I couldn't find it. Can you provide me with the link please?
Praveen Kumar Gudipudi 1,495 Reputation points Microsoft External Staff Moderator

2025-11-11T17:58:14.3066667+00:00

Hello Griet Van Compernolle,

Please check blow document: https://learn.microsoft.com/en-us/community/content/compare-extensibility-options-azure-logic-apps-standard
Griet Van Compernolle 0 Reputation points

2025-11-11T19:30:06.14+00:00

My workflow with inline code action doesn't call custom C# assemblies. The same issue occurs even when adding the C# inline script action with the sample code.

Concerning the workflow which has a local function action, the corresponding DLL is packed in a custom folder (lib\custom\net8).
Griet Van Compernolle 0 Reputation points

2025-11-12T08:06:24.0266667+00:00

See my feedback underneath which I wrongly added as Answer :)
Praveen Kumar Gudipudi 1,495 Reputation points Microsoft External Staff Moderator

2025-11-12T11:49:53.0133333+00:00
Hello Griet Van Compernolle,

This is happening because your C# inline code is using a reference to Newtonsoft.Json but the Logic Apps runtime (the Workflow runtime for local functions) is using a different version of that assembly internally.

Method not found: 'Newtonsoft.Json.Linq.JToken.get_Outputs()'

means your function was compiled against one version of Newtonsoft.Json, but at runtime, Logic Apps is loading another version and that method signature doesn’t exist there.

Resolution options

Option 1 — Use Logic Apps’ built-in Newtonsoft.Json

Logic Apps Standard runtime already includes a compatible version of Newtonsoft.Json.
You don’t need to add or reference your own copy.

Fix:

Remove your custom DLL reference for Newtonsoft.Json.

In your .csx or .cs file, just keep:

using

Don’t ship your own Newtonsoft.Json.dll inside lib\custom\net8.

Then redeploy the workflow and test again.

Option 2 — Explicitly match the runtime version

If you must bring your own Newtonsoft.Json (for example, to use features from a newer version):

Add a binding redirect in your host.json or csproj:

<ItemGroup

Rebuild the project so your function app and Logic App share the same assembly version.

Ensure the assembly gets copied to bin when building:

<CopyLocalLockFileAssemblies

But again — this can still be brittle, since Logic Apps may override that dependency at runtime.

Option 3 — Move JSON manipulation to inline code

If your function only removes nulls from JSON, you can safely do it inline with built-in System.Text.Json:

using

This uses System.Text.Json, which is fully supported by Logic Apps Standard without any external assemblies.
Praveen Kumar Gudipudi 1,495 Reputation points Microsoft External Staff Moderator

2025-11-20T16:45:54.66+00:00

Hello Griet Van Compernolle,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Griet Van Compernolle 0 Reputation points

2025-11-20T18:46:25.58+00:00

Mixing inline scripting & local functions inside one logic app doesn't seem to work. As soon a custom library (which is needed for the local function) is available in the logic app, the inline script function doesn't work anymore.

Since our logic app contains workflow which requires a local function action (https://learn.microsoft.com/en-us/azure/logic-apps/create-run-custom-code-functions), we created our inline script as another function. Like this we don't encounter this conflict anymore.

1 answer

Your answer

Praveen Kumar Gudipudi 1,495 Reputation points Microsoft External Staff Moderator

2025-11-10T17:15:14.99+00:00

Hello Griet Van Compernolle,

Are you calling C# Inline Script action logic app from custom actions logic app?
Griet Van Compernolle 0 Reputation points

2025-11-10T19:40:33.42+00:00

I have one logic app with 2 workflows:

1 workflow contains a local function action (https://learn.microsoft.com/en-us/azure/logic-apps/create-run-custom-code-functions).

1 workflow contains a C# inline script action

Both actions are separate, and doesn't call each other.
Praveen Kumar Gudipudi 1,495 Reputation points Microsoft External Staff Moderator

2025-11-11T17:19:47.8433333+00:00

Hello Griet Van Compernolle,

This is a known issue when mixing the two scripting types in one Logic App (especially in Standard tier). Microsoft’s documentation notes that “Inline Code and Custom Code actions should not be mixed within the same Logic App.

You have a few options:

Split into separate Logic Apps

Create two separate Logic Apps:

One for your Local Function action

Another for your Inline C# action

This completely isolates the runtimes, preventing version conflicts.
Griet Van Compernolle 0 Reputation points

2025-11-11T17:37:08.0166667+00:00

I've checked the documentation but I couldn't find it. Can you provide me with the link please?
Praveen Kumar Gudipudi 1,495 Reputation points Microsoft External Staff Moderator

2025-11-11T17:58:14.3066667+00:00

Hello Griet Van Compernolle,

Please check blow document: https://learn.microsoft.com/en-us/community/content/compare-extensibility-options-azure-logic-apps-standard
Griet Van Compernolle 0 Reputation points

2025-11-11T19:30:06.14+00:00

My workflow with inline code action doesn't call custom C# assemblies. The same issue occurs even when adding the C# inline script action with the sample code.

Concerning the workflow which has a local function action, the corresponding DLL is packed in a custom folder (lib\custom\net8).
Griet Van Compernolle 0 Reputation points

2025-11-12T08:06:24.0266667+00:00

See my feedback underneath which I wrongly added as Answer :)
Praveen Kumar Gudipudi 1,495 Reputation points Microsoft External Staff Moderator

2025-11-12T11:49:53.0133333+00:00

Hello Griet Van Compernolle,

This is happening because your C# inline code is using a reference to Newtonsoft.Json but the Logic Apps runtime (the Workflow runtime for local functions) is using a different version of that assembly internally.

Method not found: 'Newtonsoft.Json.Linq.JToken.get_Outputs()'

means your function was compiled against one version of Newtonsoft.Json, but at runtime, Logic Apps is loading another version and that method signature doesn’t exist there.

Resolution options

Option 1 — Use Logic Apps’ built-in Newtonsoft.Json

Logic Apps Standard runtime already includes a compatible version of Newtonsoft.Json.
You don’t need to add or reference your own copy.

Fix:

Remove your custom DLL reference for Newtonsoft.Json.

In your .csx or .cs file, just keep:

using

Don’t ship your own Newtonsoft.Json.dll inside lib\custom\net8.

Then redeploy the workflow and test again.

Option 2 — Explicitly match the runtime version

If you must bring your own Newtonsoft.Json (for example, to use features from a newer version):

Add a binding redirect in your host.json or csproj:

<ItemGroup

Rebuild the project so your function app and Logic App share the same assembly version.

Ensure the assembly gets copied to bin when building:

<CopyLocalLockFileAssemblies

But again — this can still be brittle, since Logic Apps may override that dependency at runtime.

Option 3 — Move JSON manipulation to inline code

If your function only removes nulls from JSON, you can safely do it inline with built-in System.Text.Json:

using

This uses System.Text.Json, which is fully supported by Logic Apps Standard without any external assemblies.
Praveen Kumar Gudipudi 1,495 Reputation points Microsoft External Staff Moderator

2025-11-20T16:45:54.66+00:00

Hello Griet Van Compernolle,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Griet Van Compernolle 0 Reputation points

2025-11-20T18:46:25.58+00:00

Mixing inline scripting & local functions inside one logic app doesn't seem to work. As soon a custom library (which is needed for the local function) is available in the logic app, the inline script function doesn't work anymore.

Since our logic app contains workflow which requires a local function action (https://learn.microsoft.com/en-us/azure/logic-apps/create-run-custom-code-functions), we created our inline script as another function. Like this we don't encounter this conflict anymore.

Answer 1

Hello Griet Van Compernolle,

Thanks for the update.

Issue: C# Inline Scripting doesn't work anymore when custom functions are used.

Resolution: Mixing inline scripting & local functions inside one logic app doesn't seem to work. As soon a custom library (which is needed for the local function) is available in the logic app, the inline script function doesn't work anymore.

Since our logic app contains workflow which requires a local function action (https://learn.microsoft.com/en-us/azure/logic-apps/create-run-custom-code-functions), we created our inline script as another function. Like this we don't encounter this conflict anymore.

User's image

Please accept as answer and do a Thumbs-up to upvote this response if you are satisfied with the community help. Your upvote will be beneficial for the community users facing similar issues.

Share via

C# Inline Scripting doesn't work anymore when custom functions are used

Split into separate Logic Apps

Resolution options

Option 1 — Use Logic Apps’ built-in Newtonsoft.Json

Option 2 — Explicitly match the runtime version

Option 3 — Move JSON manipulation to inline code

1 answer

Your answer