Start message webhook always returns 500

Camunda 8 Topics Discussion & Questions
,
2

Hi there! :waving_hand:

I can see you’re experiencing a known issue with the HTTP Webhook connector in Camunda 8.6.x versions. The NullPointerException in InboundWebhookRestController.escapeValue is a documented problem related to template version mismatches and response expression handling.

Root Cause

This issue occurs due to incompatibilities between the connector template version and the runtime expectations in Camunda 8.6.x, particularly when using response expressions.

Solution

Based on the forum discussions you referenced and similar cases, here’s the recommended workaround:

1. Update your BPMN XML manually:

  • Set the template version to 10 in your BPMN file
  • Use inbound.responseBodyExpression instead of inbound.responseExpression

Edit your BPMN XML to include:

zeebe:modelerTemplateVersion="10"

And ensure you’re using the correct property name for the response expression.

2. Verify your connector configuration:

  • Make sure you’re using the latest connector template for Camunda 8.6
  • Validate that your FEEL expressions are correctly formatted
  • Ensure all referenced variables exist in the incoming request

3. Check your result expression:

Since you mentioned using result expression modification, make sure:

  • Your result expression is valid FEEL syntax
  • It only references available data (like request.body.requestId)
  • No null values are being passed to the escapeValue method

If the workaround doesn’t work:

This appears to be a bug in Camunda 8.6.x versions. If the above solution doesn’t resolve your issue, I’d recommend:

  1. Filing a bug report at: Issues · camunda/camunda · GitHub
  2. Include your BPMN file, connector configuration, and the full stack trace
  3. Mention this is related to the InboundWebhookRestController.escapeValue NullPointerException

References:

Let me know if you need help implementing these changes or if the issue persists after trying the workaround!