I am trying to setup a webhook on a specific project but get an error response from Asana “This resource already has too many webhooks, and no more can be added to it”.
#response
HTTP/1.1 403
{
“errors”: [
{
“message”: “This resource already has too many webhooks, and no more can be added to it.”,
“help”: “For more information on API status codes and how to handle them, read the docs on errors: Errors”
}
]
}
I know about the limit on the number of webhooks per resource and checked if that is the case. I was not able to find a single webhook on the resource I am trying to create a webhook on.
@Dawood_Aijaz - are you specifying a resource and target (blank in your example but assuming you just removed them for privacy reasons)? Have you set up webhooks successfully on other resources?
@Dawood_Aijaz - gotcha, just making sure everything in the request was squared away. Are you able to create webhooks on other resources? How did you check for existing webhooks on your resource? If you haven’t already, you can call this endpoint with a GET request and pass in your workspace and resource ID to confirm what’s already been set up there.
Is this the same issue you had in this thread from a year ago? If so, was it ever resolved?
Yes, I am able to create webhooks on other projects and Yes, I am already checking if the webhook was created using the provided API.
The issue in the old thread was resolved but this is the same issue again but with a different resource. Previously I sent the details to @AndrewWong and he did something at his and after that, I was able to create the webhook on the resource.
@Dawood_Aijaz, do you remember more specifically what the issue was last time? It looks like you are aware of the 1,000 webhook limit per resource but I’ll mention that again for others that might be looking for a reason for this error.
The limit is enforced globally (across all API tokens) and your token or app may not be able to see or modify webhooks subscriptions created from other apps.
Hi @John_Baldo,
Here’s the response from @AndrewWong regarding the issue we discussed in DM:
"A single user seems to be using event streams, not webhooks, to create the subscriptions. That is, it looks like several hundred requests were made to GET /events?resource=gid by a single user, but the sync token was never actually used to fetch events.
We’ve helped clean up the expired consumers. You should be able to create webhooks on that project now."