Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Webhook Start Event Not Functioning in Camunda 8.3.x, SaaS #1373

Closed
ikheraj17 opened this issue Nov 6, 2023 · 4 comments
Closed

Webhook Start Event Not Functioning in Camunda 8.3.x, SaaS #1373

ikheraj17 opened this issue Nov 6, 2023 · 4 comments
Assignees
Labels
kind:bug Something isn't working

Comments

@ikheraj17
Copy link

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.
Screen Shot 2023-11-06 at 12 41 05 PM
Please find the process diagram at hand here.

Steps to Reproduce

  1. Download the BPMN file attached to this ticket and upload to Camunda 8 Web Modeler.

  2. Deploy diagram to a 8.3.x Zeebe cluster.

  3. Note that the 'Webhook' tab in the properties panel for the start element does not show an active webhook

  4. Test the webhook and notice the absence of expected response

  5. 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
@ikheraj17 ikheraj17 added the kind:bug Something isn't working label Nov 6, 2023
@chillleader
Copy link
Member

Hi @ikheraj17, thank you for your report. This behavior is expected: in 8.3.0 the Webhook connector response doesn't have a body by default.

Instead, it is now possible to configure a custom response body. There's an example here (see 8. Response body expression).

@alexcorremans
Copy link

alexcorremans commented Nov 14, 2023

Hey @chillleader, since this looks like a breaking change for this customer, could this be added to the update guide and the announcements page?

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?

@chillleader
Copy link
Member

chillleader commented Nov 16, 2023

Hey @alexcorremans I have created a task to fix this - the docs update has a high priority, we will tackle it soon.

I will close this issue once the docs are updated, @ikheraj17 please let us know if you have any issues with the new functionality.

@chillleader
Copy link
Member

The docs update is merged and will be released soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants