Azure, Logic App Standard node.js upgrade from 22 to 24 gives error in Transform XML using XSLT map action

Question

Azure, Logic App Standard node.js upgrade from 22 to 24 gives error in Transform XML using XSLT map action

Annica Andersson | Kazoku IT 0

Error:

InternalServerError

Exception while executing function: Functions.XsltNetFxLanguageWorkerFunction

xslt version 1.0

Changing back to node.js 22 and it works fine again

Is there a known issue or limitation between the XSLT worker (XsltNetFxLanguageWorkerFunction) and Node.js 24?

What do you recommend: changing back to Node.js 22, upgrading the XSLT version, or something else?

Hemant Bharadwaj 370 Reputation points Microsoft Employee

2026-11-06T15:52:55.1133333+00:00
Likely cause/summary: this looks like a runtime compatibility issue in the XSLT worker path after switching Node 22 -> 24, not an XSLT map content problem (since rollback to 22 works).

Confirm worker/runtime support matrix for your Logic App Standard stack.

Validate your Logic App runtime version and extension bundle compatibility with Node 24.

If unsupported, stay on Node 22 in production until Microsoft confirms support.

Isolate by minimal repro.

Run a minimal workflow with a tiny XSLT 1.0 map and same action to confirm platform-level behavior.

Capture exact run IDs, timestamp, and full action error payload.

Check known regressions and pin versions.

Pin to the previously working runtime/host settings while investigating.

Re-test after platform/runtime updates.

Safe mitigation/rollback.

Keep Node 22 for this workflow path, deploy Node 24 tests to a separate slot/environment, and cut over only after successful validation.

References:

https://learn.microsoft.com/azure/logic-apps/single-tenant-overview-compare

https://learn.microsoft.com/azure/logic-apps/create-single-tenant-workflows-visual-studio-code

https://learn.microsoft.com/azure/logic-apps/logic-apps-diagnosing-failures

“If you find this answer helpful, please upvote it. If this resolves your issue, please mark it as the accepted answer so that it can help others in the community.”

1 answer

Your answer

Hemant Bharadwaj 370 Reputation points Microsoft Employee

2026-11-06T15:52:55.1133333+00:00

Likely cause/summary: this looks like a runtime compatibility issue in the XSLT worker path after switching Node 22 -> 24, not an XSLT map content problem (since rollback to 22 works).

Confirm worker/runtime support matrix for your Logic App Standard stack.

Validate your Logic App runtime version and extension bundle compatibility with Node 24.

If unsupported, stay on Node 22 in production until Microsoft confirms support.

Isolate by minimal repro.

Run a minimal workflow with a tiny XSLT 1.0 map and same action to confirm platform-level behavior.

Capture exact run IDs, timestamp, and full action error payload.

Check known regressions and pin versions.

Pin to the previously working runtime/host settings while investigating.

Re-test after platform/runtime updates.

Safe mitigation/rollback.

Keep Node 22 for this workflow path, deploy Node 24 tests to a separate slot/environment, and cut over only after successful validation.

References:

https://learn.microsoft.com/azure/logic-apps/single-tenant-overview-compare

https://learn.microsoft.com/azure/logic-apps/create-single-tenant-workflows-visual-studio-code

https://learn.microsoft.com/azure/logic-apps/logic-apps-diagnosing-failures

“If you find this answer helpful, please upvote it. If this resolves your issue, please mark it as the accepted answer so that it can help others in the community.”

Answer 1

Thank you for your response.

Since reverting to Node.js 22 immediately resolves the issue, we believe we have sufficiently demonstrated that the problem is related to the runtime/platform behavior introduced with Node.js 24 rather than to the map content itself.

We have also observed the same behavior with XSLT 3.0, which indicates that the issue is not specific to XSLT 1.0.

As this is a customer production environment, we cannot justify spending additional time on extensive troubleshooting or creating further test scenarios when the issue is already reproducible and isolated to the Node.js 24 upgrade.

We therefore request clarification from the product team on one of the following:

Is Node.js 24 officially supported for Logic Apps workloads using the Transform XML/XSLT functionality?

Are there any additional configuration changes, feature flags, runtime settings, extension bundle versions, or migration steps required when upgrading from Node.js 22 to Node.js 24?

Is this a known issue or regression in the XSLT worker/runtime path?

If additional configuration is required for Node.js 24, please provide the relevant documentation or guidance. Otherwise, we would appreciate confirmation that this is a platform issue together with a recommended resolution or workaround.