[GH-ISSUE #47] When using CHECK_POSTS_IN_HOURS_RANGE, 'next check' should factor that in #35

New issue

Closed

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

kerem commented

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

Owner

Originally created by @tomballgithub on GitHub (Jan 17, 2026).
Original GitHub issue: https://github.com/misiektoja/instagram_monitor/issues/47

Current logic goes to sleep for X time and then evaluates if within the window for CHECK_POSTS_IN_HOURS_RANGE.
The web dashboard has a very clear 'Next Check' indication.

However, since the dashboards present this so prominently, it should include consideration for CHECK_POSTS_IN_HOURS_RANGE.

So, for example, currently my Next Check says 14:56, but my hours range is 09:00 - 10:59, 21:00 - 22:59.
For accuracy, shouldn't the Next Check always be within the next available hour range?

This is about ensuring accuracy to the user.

Console dashboard shows a 'Next Chk' column with same issue. Mine says "14:40", but my hours range is 09:00 - 10:59, 21:00 - 22:59.

Originally created by @tomballgithub on GitHub (Jan 17, 2026). Original GitHub issue: https://github.com/misiektoja/instagram_monitor/issues/47 Current logic goes to sleep for X time and then evaluates if within the window for CHECK_POSTS_IN_HOURS_RANGE. The web dashboard has a very clear 'Next Check' indication. However, since the dashboards present this so prominently, it should include consideration for CHECK_POSTS_IN_HOURS_RANGE. So, for example, currently my Next Check says 14:56, but my hours range is 09:00 - 10:59, 21:00 - 22:59. For accuracy, shouldn't the Next Check always be within the next available hour range? This is about ensuring accuracy to the user. Console dashboard shows a 'Next Chk' column with same issue. Mine says "14:40", but my hours range is 09:00 - 10:59, 21:00 - 22:59.