Hello,

We have noticed that webhooks for Instagram comments are not always being sent to our platform, despite us having a working webhook subscription. We are receiving webhooks for the majority of comments, so we know that it is not an issue with the webhook subscription, however we are noticing that a significant amount of comments exist on the post but never get sent to our platform as a new comment webhook. We are seeing this issue on a number of different client accounts, which leads us to believe that this may be affecting a portion of all Instagram new comment webhooks.

This is following upon a related Bug Report (https://developers.facebook.com/support/bugs/3268884103406735/) that was never resolved.

After observing this bug for the past month, we have some guesses as to what might be happening and would appreciate any insights on how to address this issue. Here is an example that we have observed today: * We received a webhook for an IG comment with the ID 18331437253131859, but we receive this error when we try to access it via the Graph API Explorer via /18331437253131859: * "Unsupported get request. Object with ID '18331437253131859' does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api" . * Crawling the /comments edge for the post that that comment was made on 18048023956707535?fields=comments{username,text,id,hidden,timestamp} surfaced another comment ID 18029388176026542 that has the exact same username and text, but the timestamp was 3 seconds later. We DID NOT receive a webhook for this comment. We are able to access that comment via the Graph API Explorer via /18029388176026542 using the same access token.

This makes me wonder if somehow the comment is being double posted (either by the user or by IG's backend), but a webhook is only being sent for the first copy and not the second copy. And between when we got the webhook for the first comment and when we actually tried to hide that comment via POST /18331437253131859, the comment had already been deleted in favor of the second copy.