Why does this error occur when retrieving the Post ID via HTTP after posting on Instagram?
Error: Couldn’t reach Instagram from CreatePostPhoto in this module. The app hit its request limit while posting.
Possible fixes:
Wait and run the scenario again later.
Reduce post frequency in this route.
Add a longer Delay field before CreatePostPhoto.
How to solve this?
That message is a publishing rate limit rather than anything wrong with your HTTP call, so retrieving the post ID is not the thing that failed. The container was created and then the publish was refused.
Instagram limits how many posts an account can publish through the API in a rolling 24 hour window, and it is counted per account rather than per app or per scenario. Adding a delay before the module helps only if you are genuinely bunching posts together in one run. If you have already used the window up, waiting is the only thing that clears it, and it clears gradually as older posts age out rather than resetting at midnight.
The useful part is that you do not have to guess where you stand. There is an endpoint that reports your current usage against that window: GET on your IG user ID with the content publishing limit field returns how many posts you have published in the last 24 hours. Call it before publishing and you can decide to skip or queue rather than firing into a refusal. That turns an unpredictable error into a check you control.
On the post ID itself, once publishing succeeds the publish call returns the media ID in its response, so you do not need a separate lookup for it. If you are calling something extra afterwards to fetch it, that call is probably what is burning through your requests.