- Community
- Question
We have an issue with GET /{user-id}/media API. Occasionally it returns error during certain period of time, and after that it works again. We have retry mechanism, but it is not sufficient.
I have reproduced the issue using Graph API Explorer. The session id is session_id=2492201104292272. Furthermore we noticed is that for the same API call sometimes we get "An unknown error occurred" and sometimes it is "Please reduce the amount of data you're asking for, then retry your request". On the picture that I uploaded is an example of "Unknown error".
We still have this issue. We noticed that the same behaviour we have for the same Facebook and Instagram account (when I say the same, i mean the same account but different id, since there is separate id for IG and FB). The endpoint that fails: for FB: v16/{facebook_page_id}/video_reels for IG: v16/{user-id}/media For FB endpoint we created separate thread, but once again, it is related to the same account as I mentioned at the beginning https://developers.facebook.com/community/threads/691539356228969
Furthermore, We have retry mechanism, that trigger API call up to 9 times with time span between calls that has geometric progression increase (2, 4, 8, 16... 512 sec). Even with this mechanism we cannot collect all necessary data, since specific APIs are unavailable within much longer period of time (like hours)
I have similar issue. I have a tool that requests /{user-id} media path every 10 minutes and the tool has been having a 400 error since 09/18 19:20UTC. At least the tool hasn't succeeded so far. What is your http code?
We get 500, with two different error messages as I wrote. Sometimes it return 500 with "Please reduce the amount of data you're asking for, then retry your request", but sometimes 500 with "An unknown error occurred", and sometimes the same API works.
Thank you. It seems the issue you're facing is difference from mine. I still can't succeed to call {ig-user-id}/media path since 9/19. If it's not caused by an incident, I believe there was a behavior change on Instagram Graph API. I keep investigating as possible as but I think I have to wait for the sufficient info about that... (I'm not sure Instagram documents or nor)