We are experiencing issues with the Instagram Basic Display API and would appreciate any insight or assistance from the community.
Issue Description. When making a GET request to https://graph.instagram.com/v19.0/me on the Instagram Basic Display API, the error in the attached capture occurs. The HTTP Status Code returns a 500 Internal Server Error. This issue occurred at 21:10 UTC on 8/27/2024 and is still ongoing. Currently, user information cannot be Acquisition.
Also, the application mode is in live mode and public_profile and instagram_graph_user_profile are allowed advanced access.
Has anyone encountered this issue or know of a solution? Any information about possible causes or workarounds would be appreciated. Best regards!

When using the Instagram Graph API to retrieve conversations, I am experiencing an issue where the cursor "after" value remains the same, and the data for the next page is identical to the first page. Despite multiple requests, the cursor does not update, which prevents access to subsequent data pages. Example API call: /v20.0/[fb_page_id]/conversations?platform=instagram&fields=id,name,participants,updated_time,messages.limit(1),subject&limit=5 Response:
{ "data": [...], "paging": { "cursors": { "after": "ZAXlKMGFXMWxjM1JoYlhBaU9qRTNNak0xTkRRMk5qTXpNamNzSW5Sb2NtVmhaQUY5cFpBQ0k2SWpNME1ESTRNak0yTmpnME1UY3hNRE13TVRJME5ESTFPVFkyT1RFM09EVXpNak01T1Rnek55SjkZD" }, "next": "......" } }
The cursor "after" value does not change, and the result remains the same for the next page. It is a bug.
This problem persists and prevents pagination from working correctly. Could you provide guidance on how to resolve this issue?
Thank you for your assistance.

Starting yesterday we are seeing several instagram conversations returning a non valid timestamp:
"updated_time": "56454-04-04T18:29:15+0000"
This is the endpoint we are currently using: me/conversations?fields=id,updated_time&platform=instagram
It does not seem to be a widespread issue but the amount of affected accounts is quite important right now. Does anybody know if that is something already reported to Meta?
Thanks in advance!

Problem
I am trying to fetch Insights data along with media data using the Media API. However, when the response includes media with media_product_type: 'REELS', the error occurs.
Is this a bug? If not, could you please advise on how to handle this issue?
Endpoint
GET /{ig-user-id}/media v18.0 https://developers.facebook.com/docs/instagram-platform/instagram-graph-api/reference/ig-user/media
Request Sample
https://graph.facebook.com/v18.0/{ig-user-id}/media?fields=id,media_type,media_product_type,timestamp,like_count,comments_count,media_url,thumbnail_url,children%7Bmedia_url%7D,caption,permalink,insights.metric(impressions,profile_visits,follows,reach,saved)&limit=25&access_token={access_token}
Response
{
"error": {
"message": "(#100) The Media Insights API does not support the impressions, profile_visits, follows metric for this media product type.",
"type": "OAuthException",
"code": 100,
"fbtrace_id": "A9hTiVk7AgYkpTBap84AC8c"
}
}

IG Story permalink fields used to be in a format that would actually link out to the story.
Ex: https://www.instagram.com/stories/{username}/{id}
As of 7/17 the API is returning them in the shortcode format which is no longer a working link.
Ex: https://www.instagram.com/p/C9nd1hSzKn/
When attempting to navigate to the shortcode link we receive an error page with: "Sorry, this page isn't available. The link you followed may be broken, or the page may have been removed. Go back to Instagram."
This is consistent across all users.
Is this an intended change? How should we be able to resolve the actual linkable story URL if so?