Troubleshooting

Common problems

“The value '/serviceProviders/lamboXsltCompose' … is not valid”, or the action is missing

The runtime is loading the extension bundle. Remove extensionBundle from the host.json the runtime reads (build and publish output), and in Azure delete the AzureFunctionsJobHost__extensionBundle__* app settings.

LicenseRequired: Lambogenius Compose using XSLT requires a license

LAMBOGENIUS_LICENSE is not set and the host isn't func start on a developer machine. Set it to a developer, trial or production token from lambogenius.com/app/licensing; the change applies within 5 minutes.

LicenseRequired: … is not a valid license token / is not for Compose using XSLT

The setting holds something else: an HL7, Liquid or CLI license, a truncated paste, or an unresolved Key Vault reference (check the Logic App's identity can read the secret).

WorkerUnavailable: the worker could not be started

xslt-worker/ is missing or incomplete in the deployed folder, or the .NET 8 runtime is not available. Deploy the publish output; check xslt-worker/Lambogenius.XsltCompose.Worker.dll and its .runtimeconfig.json. On Linux, use 1.1.1 or later and check xslt-worker/linux-x64/.

The first call is slow

Worker start and compilation, about 0.3–1 s plus 1–1.5 s for C#. Later calls hit the per-worker cache.

ScriptsDisabled

Set enableScripts to true on the action; check XsltCompose__AllowScripts.

FunctionNotAllowed

Add the alias to allowedFunctionAliases and to the registry; check XsltCompose__AllowedFunctionAliases and that the registry file is valid.

FunctionAuthenticationFailed: the app setting … is not set

The registry's keySetting names an app setting that does not exist. Add it, ideally as a Key Vault reference.

MapNotFound

mapName is relative to the map folder and uses /. The message names the missing module and where it is referenced.

xpath() on the result fails

result is a string: wrap it with xml(...). For JSON text, use json(...).

The designer doesn't show the action

The VS Code designer loads built-in connectors from the extension bundle. Workflows authored as JSON still run.

Still stuck? Email hello@lambogenius.com with the error message and its correlation ID (no payload data).