[GH-ISSUE #34] Issue with fetching latest post when pinned posts are present #23

New issue

Closed

opened 2026-02-27 20:05:02 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 20:05:02 +03:00

Owner

Originally created by @jl-nr on GitHub (Jan 6, 2026).
Original GitHub issue: https://github.com/misiektoja/instagram_monitor/issues/34

I spotted something interesting. When a user has pinned posts, it correctly detects the latest one in session mode, even if that's not the pinned one. But when using anonymous mode, it seems to always report the first pinned post. Bug?

Originally created by @jl-nr on GitHub (Jan 6, 2026). Original GitHub issue: https://github.com/misiektoja/instagram_monitor/issues/34 I spotted something interesting. When a user has pinned posts, it correctly detects the latest one in session mode, even if that's not the pinned one. But when using anonymous mode, it seems to always report the first pinned post. Bug?

kerem closed this issue

2026-02-27 20:05:02 +03:00

kerem commented

2026-02-27 20:05:03 +03:00

Author

Owner

@misiektoja commented on GitHub (Jan 6, 2026):

Thanks for pointing that out! You're absolutely correct. I missed this because none of my test accounts have pinned posts, so it totally slipped under the radar.

It seems like the tool is only checking the very first item in the API response (edges[0]) when in anonymous mode. And since pinned posts grab those top spots, the tool wrongly assumes the first pinned post is the latest, which means it’s ignoring all the exciting new updates below. I was aiming to keep request numbers low to dodge Instagram's radar, but I might have gone a bit overboard with it. Luckily, it shouldn't be too hard to fix!

@misiektoja commented on GitHub (Jan 6, 2026): Thanks for pointing that out! You're absolutely correct. I missed this because none of my test accounts have pinned posts, so it totally slipped under the radar. It seems like the tool is only checking the very first item in the API response (edges[0]) when in anonymous mode. And since pinned posts grab those top spots, the tool wrongly assumes the first pinned post is the latest, which means it’s ignoring all the exciting new updates below. I was aiming to keep request numbers low to dodge Instagram's radar, but I might have gone a bit overboard with it. Luckily, it shouldn't be too hard to fix!

kerem commented

2026-02-27 20:05:03 +03:00

Author

Owner

@misiektoja commented on GitHub (Jan 6, 2026):

Issue fixed and is available in the latest beta v2.1 on the dev branch: instagram_monitor.py

@misiektoja commented on GitHub (Jan 6, 2026): Issue fixed and is available in the latest beta v2.1 on the dev branch: [instagram_monitor.py](https://raw.githubusercontent.com/misiektoja/instagram_monitor/refs/heads/dev/instagram_monitor.py)

kerem referenced this issue

2026-02-27 20:05:12 +03:00

[PR #23] [MERGED] Added messaging for sleep time if HOURS_VERBOSE to give insight into when next check will be #56