[GH-ISSUE #48] Next Check timing not updated after check is started #34

New issue

Closed

opened 2026-02-27 20:05:05 +03:00 by kerem · 1 comment

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/48

I just restarted the script into the console dashboard.

I am seeing:

Global Next Check: 14:40
Next Chk: 14:40 (account 1)
Next Chk: 15:25 (account 2)

However, the time is currently 14:44, past those 14:40 times, which were when I launched the script.

Is this an issue of the 'next check' is not updated until the 'current check' is complete? Problem is, it's not just being a few mins off, as mine is going to take 45 mins (4000+ followings).

Proposal: Changing the 'Next Chk' for the user, for which my status says "Downloading Followings" could be "In Progress" instead of "14:40".

Proposal: Update Global Next Check to the next known GNC once the current one starts, or also "In Progress"

Originally created by @tomballgithub on GitHub (Jan 17, 2026). Original GitHub issue: https://github.com/misiektoja/instagram_monitor/issues/48 I just restarted the script into the console dashboard. I am seeing: - Global Next Check: 14:40 - Next Chk: 14:40 (account 1) - Next Chk: 15:25 (account 2) However, the time is currently 14:44, past those 14:40 times, which were when I launched the script. Is this an issue of the 'next check' is not updated until the 'current check' is complete? Problem is, it's not just being a few mins off, as mine is going to take 45 mins (4000+ followings). Proposal: Changing the 'Next Chk' for the user, for which my status says "Downloading Followings" could be "In Progress" instead of "14:40". Proposal: Update Global Next Check to the next known GNC once the current one starts, or also "In Progress"

kerem closed this issue

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

kerem commented

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

Author

Owner

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

Yes, in the current implementation, the next check is delayed until the current check is completed. I will change it. I'm not sure what the best approach will be since we cannot determine the real next check until we finish processing, but maybe something like "In progress" you suggested.

@misiektoja commented on GitHub (Jan 18, 2026): Yes, in the current implementation, the next check is delayed until the current check is completed. I will change it. I'm not sure what the best approach will be since we cannot determine the real next check until we finish processing, but maybe something like "In progress" you suggested.