Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Webhook Returning Empty Response Error
I have 3 apps that are configured identically. 2 Development and 1 production.
Each has a webhook URL specified. The live production one keeps erroring out with the below error. I can immediately r...
Greg-DB
Dropbox Community Moderator
Dropbox Community ModeratorThanks for following up. In that case, please do please open an API ticket with the relevant app key(s) and webhook URI(s) so we can investigate this failure for you. We can also check our logs for see what happened with the email. Please make sure to open the ticket while signed in to the account that owns the app in question.
And thanks for the feedback regarding the disabling behavior. I can't speak to why the system was originally designed in this way, but I'll pass this feedback along to the team.
Hi Greg-DB
Thanks for the quick followup; we did open a ticket and got a quick response. There is no clear resolution however we got some additional information and will be able to monitor more closely for a future incident.
They did confirm the email was sent, so it's not clear why it wasn't delivered via G-Suite. We are getting more details on the address the email was sent from and will investigate further. They are also passing along to engineering the request to make this mechanism more robust.
If the issue occurs again and we get further information, we will update this thread.
Thanks again!
Derek
Hi Greg,
I have had this same problem again.
No email again, although after re-adding it and then disabling again, I did finally get an email. The email I needed of course would have been 3 days before when it started.
The problem represents itself the same way as before; 1) disabling and enabling again works, but returns the same error, originally the exact same response from 3 days before, so it really didn't do anything. 2) Adding the same URL again verifies just fine, becomes enabled, but still no events. 3) removing both and re-adding the URL results in an HTTP failure effectively:
HTTP/1.1 N/A Unknown
Response Body (First 256 bytes):
(No response body)"4) I was finally able to get this working, by adding the same exact URL but adding a query string of `?qs` (a garbage string but enough to slightly change the URL). It also verified fine, and now is working again.
I opened an API ticket (#10716976) but this is the same basic problem we've seen 4 or 5 times earlier and that presents itself every few months.
Derek
About Discuss Dropbox Developer & API
Make connections with other developers
