-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
WebHooks wont update the database with the user's change until you respond with 200 OK. #3575
Comments
AFAIK:
Please give more details about the data flow you mean, because I did not quite get it yet. |
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. |
Is there a bounty set for this? I'd be happy to help fund it :) |
It is possible to fund this with 500 euro at https://wekan.team/commercial-support/ This has not been funded yet. |
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)?
The text was updated successfully, but these errors were encountered: