Troubleshooting

Common problems

The sender gets AR/CR and no run starts

Check the log for the license message: messages are rejected without a valid LAMBOGENIUS_LICENSE token. Also check rejectInvalidMessages: messages without MSH-9, -10, -11 or -12 are rejected.

Actions fail with HTTP 403

No valid license, or LamboHl7Mllp__Security__RequireTls is true and the connection doesn't use TLS. The error message names the reason.

“The value '/serviceProviders/lamboHl7Mllp' … is not valid”

The host is using the extension bundle instead of the project's packages. Remove the extensionBundle section from the host.json the runtime reads (build and publish copies).

The trigger never fires in Azure

Logic Apps on App Service (WS1–WS3) can't accept inbound TCP on the trigger's port. Use the gateway, or host the Logic App where it can open ports (hybrid deployment, a container).

“could not listen for MLLP on …”

Another workflow or process uses the port. Give each receiving workflow its own connection and port.

Senders time out in Workflow mode

Keep responseTimeoutSeconds below the sender's ACK timeout, prefer stateless workflows, and make sure every path calls Send acknowledgement.

The TLS handshake fails

Both sides must use the same TLS version (1.2 or 1.3). Check the server name, the trusted thumbprints, and that the certificate includes its private key.

The ACK's MSA-2 doesn't match

validateAckControlId fails the action when the receiver acknowledges a different MSH-10. Fix the receiver, or turn the check off for that action.

The designer doesn't show HL7 MLLP

The VS Code designer loads built-in connectors from the extension bundle. Build the custom bundle and set FUNCTIONS_EXTENSIONBUNDLE_SOURCE_URI, as the package's README describes.

Still stuck? Email hello@lambogenius.com with the run ID and the log lines around the failure (no message content).