Skip to content
LambogeniusDocs

Compose using XSLT for Azure Logic Apps

Error codes

Every error code, its HTTP status, and how to read the phase and location.

Service provider/serviceProviders/lamboXsltComposeOperation ComposeXslt, shown in the designer as Compose using XSLT.

Reading an error

A failed action's message starts with a stable code, followed by the phase, the location in the map or input when known, and a correlation ID:

InvalidXml: The input content is not well-formed XML: The 'CustomerId' start tag on line 3 position 4 does not match
the end tag of 'Order'. [phase=parseInput, location=input(4,3), correlationId=d0251a79514349b388b576dd6a7f20df]

In Logic Apps the action fails; catch it with a Scope and runAfter Failed/TimedOut. The message is in the failed action's outputs.body.message:

"Error_response": {
  "type": "Response",
  "kind": "Http",
  "inputs": {
    "statusCode": 400,
    "body": { "message": "@{first(result('Transform'))?['outputs']?['body']?['message']}" }
  },
  "runAfter": { "Transform": [ "Failed", "TimedOut" ] }
}

Codes

CodeHTTPTypical cause
LicenseRequired403No license token outside func start, a token for another product, or a license past its grace period
InvalidRequest400Missing or conflicting inputs, bad parameter names or types
InvalidXml400Malformed input XML, or a DTD
MapNotFound404The map or an included/imported module is missing
MapAccessDenied400A path outside the map folder, a URL, a link or junction
UnsupportedXsltVersion400version other than 1.0 in some module
XsltCompilationFailed400XSLT syntax error, include cycle, non-UTF-8 output encoding
TransformationFailed400Runtime XSLT error, xsl:message terminate="yes"
ScriptsDisabled400msxsl:script without enableScripts, or scripts disabled for the app
UnsupportedScriptFeature400C# outside the supported subset
ScriptCompilationFailed400C# compile error (line in the map)
ScriptExecutionFailed400A script threw or returned null
FunctionNotAllowed400Alias not allowed by the action or host, not in the registry, or an invalid registry
FunctionAuthenticationFailed502Key setting missing, no token, or the Function answered 401/403
FunctionHttpFailed502404, 408, 429, 5xx, redirect or network failure
FunctionResponseInvalid502Not 200 text/plain UTF-8, or too large
FunctionTimeout504No complete answer within the call budget
TransformationTimeout504The deadline passed; the worker was killed
ResourceLimitExceeded413 (429 when queued)A size or count limit, or the queue is full
WorkerUnavailable503The worker is missing, failed to start, or crashed
Canceled / InternalError408 / 500The run was canceled / unexpected failure