WebHooks wont update the database with the user's change until you respond with 200 OK.

[n8ores]

I have noticed today that when you enable Webhooks, if you receive the Webhook that the WeKan server wont insert the User's change into the database until you respond back from your WebHook callback.

I am assuming that this is by design, so that you can use webhooks to prevent inserts (by responding with a code that isn't 200 etc)?

[xet7]

@n8ores

AFAIK:

• Wekan Outgoing Webhooks send changes from Wekan to for example Chat, it does not save anything
• Incoming data is only with REST API, also see API usage example

Please give more details about the data flow you mean, because I did not quite get it yet.

[n8ores]

@xet7

1. I have a HTTP server receiving the webbook events from WeKan, this is not a problem.
2. When I change a custom field value, that sends a webhook event to my HTTP server which I receive using my server.
3. If my server does not respond with 200 OK (or any response) but instead keeps the connection active, then WeKan will not save my change to the custom field.
4. As soon as I give a response to the webhook then WeKan saves my change to the database.

It appears the Webhook code is blocking the change event from saving in WeKan to until after it receives a valid response from the server.

To test this. Simply create a HTTP server, and dont respond when you receive a webhook request. Make a change to a custom field and then refresh your page. The OLD value will still be populated in the field and not the new value.

As I said, this may be the desired behavior (blocking updates to the MongoDb until after a valid Webhook server response is received) as it allows developers to prevent changes from occurring if they want. But I just wanted to check as it is not documented that I can find, and probably should be.

[RyanHecht]

Is there a bounty set for this? I'd be happy to help fund it :)

[xet7]

@RyanHecht

It is possible to fund this with 500 euro at https://wekan.team/commercial-support/

This has not been funded yet.