Common problems
- The action is missing, or runs fail with “service provider not found”
- 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. Check FUNCTIONS_INPROC_NET8_ENABLED=1.
- MissingServiceProviderConnectionParameterValues
- connections.json has "parameterValues": {}. Use { "templateFolder": "" }.
- WorkerUnavailable: the worker was not found or is incomplete
- lambogenius-liquid-worker/ is missing or lacks its .runtimeconfig.json. Deploy the publish output, not the build output.
- The action runs several times
- The runtime retries 5xx failures even with retryPolicy none. Leave LiquidCompose__PlatformRetries at false, and put retryPolicy inside inputs.
- TransformationTimeout on the first run only
- The deadline includes compiling the C# block, which takes a few seconds on a fresh worker. Raise timeoutSeconds.
- UnknownFilter
- Filters use C# casing: Upcase, not upcase.
- InvalidOutputJson
- A value without ToJson, quotes around ToJson, a trailing comma from a loop, or text after the JSON value.
- ScriptExecutionFailed
- A null or missing value reached a helper (add Default: ''), Default turned a number into a string, or the helper threw.
- Blank lines in text output
- Use a dash on the right of tags (-%}) and end lines with the tag.
- An XML template from Microsoft's Liquid action renders nothing
- This action does not convert XML to JSON: read it with XmlValue and XmlValues.
- The build fails with MSB3030 in a deep folder
- The Windows 260-character path limit. Move the project to a shorter path.
Still stuck? Email hello@lambogenius.com with the error message and its correlation ID (no payload data).