You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A customer is having issues utilizing a Webhook start element to kick off a process instance; the webhook does not return the expected response in 8.3.x but works fine without modifying the process diagram in 8.2.x. I've attached a screenshot of the API calls made in Postman.
Please find the process diagram at hand here.
Steps to Reproduce
Download the BPMN file attached to this ticket and upload to Camunda 8 Web Modeler.
Deploy diagram to a 8.3.x Zeebe cluster.
Note that the 'Webhook' tab in the properties panel for the start element does not show an active webhook
Test the webhook and notice the absence of expected response
Repeat steps 2-4 with an 8.2.x. Zeebe cluster and note the response
Expected Behavior
The webhook should function properly in 8.3.x. and provide the expected response in Postman.
Hints
It seems that upon disabling the authentication and authorization tabs within the webhook element, the webhook functions in 8.3.x... Further testing needed.
Environment
Camunda version: 8.3.0 SaaS
The text was updated successfully, but these errors were encountered:
Additionally, we just had another customer reach out about the empty response body (in SUPPORT-19277) because a response body was mentioned in an earlier blog post. Can something be added to the docs for this Connector to make it more clear an empty response is expected?
Describe the Bug
A customer is having issues utilizing a Webhook start element to kick off a process instance; the webhook does not return the expected response in 8.3.x but works fine without modifying the process diagram in 8.2.x. I've attached a screenshot of the API calls made in Postman.
Please find the process diagram at hand here.
Steps to Reproduce
Download the BPMN file attached to this ticket and upload to Camunda 8 Web Modeler.
Deploy diagram to a 8.3.x Zeebe cluster.
Note that the 'Webhook' tab in the properties panel for the start element does not show an active webhook
Test the webhook and notice the absence of expected response
Repeat steps 2-4 with an 8.2.x. Zeebe cluster and note the response
Expected Behavior
The webhook should function properly in 8.3.x. and provide the expected response in Postman.
Hints
It seems that upon disabling the authentication and authorization tabs within the webhook element, the webhook functions in 8.3.x... Further testing needed.
Environment
The text was updated successfully, but these errors were encountered: