You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Webhook is disabled once in a few days
Hello, we have set up a webhook in our developer app and the webhook works fine and as expected, however it seems that once in a few days the app is disabled for unknown reason, we don`t see any exceptions in the logs or in the dropbox app console, we have also added a try catch phrase inside our webhook code so it always returns 200 even if our logic fails, we also didn`t find an exception in our logs so the logic doesn`t seem to fail.
what could cause the webhook to disable?
Providers like Dropbox might disable webhooks for reasons like too many requests too quickly, security problems, or issues with how data is sent. Make sure to read the webhook instructions and follow all rules from the provider to avoid this.
- Greg-DB
Dropbox Staff
Bk13 If Dropbox is repeatedly unable to successfully deliver webhook notifications to your webhook URI server, it will stop attempting to do so. At that point, your webhook URI will be disabled, you will be notified of this by email, and no further webhook notifications will be sent until the webhook URI is re-enabled. You should be able see any available error information, though only while the webhook URI is failing, on the app's page on the App Console.
As Здравко said, be careful how you manage your webhook URI handler; the Dropbox servers expect the response to be returned quickly. You can find more information in the Webhooks documentation.
Additionally, if there are any network issues preventing the request from reaching your server, that would also be considered a failure, and you wouldn't necessarily see exceptions from your code, so you may want to check with your network admin for any potential network issues.
Bk13 wrote:..., we have also added a try catch phrase inside our webhook code so it always returns 200 even if our logic fails, ...
Hi Bk13,
It's a mistake even to think in that direction! You logic should be executed after the web handler returned. A delay may trigger fault on Dropbox side even when you return status 200. Restructure your code and make it async.
Hope this gives direction.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
