Unable to create webhook "This resource already has too many webhooks, and no more can be added to it."

English Forum Developers & API
1

Hi Everyone,

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”.

Following is request and error response I get

request
curl --request POST
–url ‘https://app.asana.com/api/1.0/webhooks?opt_fields=’
–header ‘accept: application/json’
–header 'authorization:
–header ‘content-type: application/json’
–data ’
{
“data”: {
“resource”: ,
“target”:
}
}

#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.

Can someone please help me out with this? Thanks!

Regards,
Dawood

1 Like
2

@sasha_f @Jeff_Schneider

2 Likes
3

Thanks for pinging @Phil_Seeman. We will get back with an answer soon.

2 Likes
4

Hi @Dawood_Aijaz, you may have hit a one of the webhook limits for that resource. There’s a global limit across all users/apps, so it’s possible that other users/apps have collectively created 1,000 webhooks on that resource. It’s difficult to say for certain without knowing other details (e.g., resource gid).

2 Likes
5

Thank you @Phil_Seeman , @Jeff_Schneider and @AndrewWong ,

We are aware of the 1000 webhook limit, thanks. We stream all object versions, and all database changes including webhook subscriptions, and can assure you the limit has not been reached for this resource. The resource is 249 days old and is limited to 4 members only who all work together, so it’s not exposed to any unknown users/apps.

Is there any other limit that could return this response?

The workspace has > 6000 active webhooks from a single user.
That user is able to create new webhooks in the workspace, without this error response.

The resource is part of a migration process to a new backend where new webhooks are required. We could proceed with a workaround to recreate the project to reset the limit but it would become a much bigger problem if the issue occurred on the other resources we need to complete the migration. The resource is stuck in limbo, will it happen to more of them?

I’ve DM: ed the workspace and resource to @AndrewWong

2 Likes
6

Hi @AndrewWong ,

Hope you are doing well. Any update on this? We are losing events on the resource.

1 Like
7

Feedback received from @AndrewWong through DM.

1 Like
8

@Dawood_Aijaz,

If/when you get a resolution on this issue, please come back and post it here so others who might encounter this thread in the future will have the benefit of that knowledge. Thanks!!

2 Likes