[GH-ISSUE #64] BE HUMAN probability is always 1? #47

New issue

Open

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

kerem commented

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

Owner

Originally created by @tomballgithub on GitHub (Feb 8, 2026).
Original GitHub issue: https://github.com/misiektoja/instagram_monitor/issues/64

I've had some debug statements in to see what's going on with BE HUMAN. My question is how is this intended to work, because "probability_for_cycle" returns "min(1.0, DAILY_HUMAN_HITS * sleep_seconds / day_seconds)" but I see it as always 1 (see below, it's calculating 28.836 for the min compare to 1)

    debug_print(f"Probability Calculation: {DAILY_HUMAN_HITS * sleep_seconds / day_seconds}") 
    debug_print(f"BeHuman: simulation start with probability {prob} for sleep_seconds of {sleep_seconds}")

I've noticed lately that I keep seeing BE HUMAN be the point at which my account gets flagged
Maybe it's the 429 issue we've been observing

[DEBUG 22:05:12] [XXX] Check #1 completed
**[DEBUG 22:05:12] [XXX] Probability Calculation: 28.836111111111112**
**[DEBUG 22:05:12] [XXX] BeHuman: simulation start with probability 1.0 for sleep_seconds of 41524**
[DEBUG 22:05:18] [XXX] BeHuman #1: explore feed peek OK
[DEBUG 22:05:34] [XXX] BeHuman #2: viewed own profile OK
[DEBUG 22:05:42] [XXX] BeHuman #3 error: cannot browse #grwm: 400 Bad Request - "fail" status, message "challenge_required" when accessing https://i.instagram.com/api/v1/tags/web_info/?__a=1&__d=dis&tag_name=grwm
[DEBUG 22:06:12] [XXX] BeHuman #4: visited followee powhub OK
[DEBUG 22:06:17] [XXX] BeHuman: simulation stop
[DEBUG 22:06:17] [XXX] Sleeping 11 hours, 32 minutes for XXX, resumes at ~09:38:21
[DEBUG 22:06:17] [XXX] Next check scheduled for: Sun 08 Feb 2026, 09:37:16
[DEBUG 22:06:17] [XXX] UI Data Update: targets=['XXX']

And here's what happened before it, no issues, even with fetching all those followings:

[DEBUG 21:23:49] [XXX] Fetching profile data from Instagram API...
[DEBUG 21:24:01] [XXX] Profile loaded: followers=191, following=4435, posts=1
[DEBUG 21:24:01] [XXX] Story available: False
[DEBUG 21:24:01] [XXX] UI Data Update: targets=['XXX']
* Followings number changed by user XXX from 4430 to 4435 (+5)
[DEBUG 21:24:01] [XXX] Writing CSV entry to kara_elaine_long.csv: Type=Followings Count, Old=4430, New=4435
* Downloading Followings: 100%|████████████████████▉| 4434/4435 [11.3 names/req, reqs=393, mins=40.7, remain=0.1][DEBUG 22:04:44] [XXX] [close_pbar] ENTRY - thread_pbar is None: False
* Downloading Followings: 100%|████████████████████▉| 4434/4435 [11.3 names/req, reqs=393, mins=40.7, remain=0.1]
[DEBUG 22:04:44] [XXX] [close_pbar] logger_instance found: True, type: FilteredWriter
[DEBUG 22:04:44] [XXX] [close_pbar] clean_final: * Downloading Followings: 99%|███████████████████░| 4,434/4,435 [11.3 names/req, reqs=393, mins=40.7, remain=0.1]
[DEBUG 22:04:44] [XXX] [close_pbar] main_log is None
[DEBUG 22:04:44] [XXX] [close_pbar] target: None, target_paths: ['XXX']
[DEBUG 22:04:44] [XXX] [close_pbar] No target, writing to all logs
* Followers: reported (191) actual (191). Followings: reported (4435) actual (4434)
* Followings (4435) actual (4434) saved to file 'instagram_XXX_followings.json'

Added followings:

XXX
* Sending email notification to XXX
* Webhook notification sent successfully

Check interval:                         10 hours, 11 minutes (Sat 07 Feb 11:54 - 22:05)
Timestamp:                              Sat 07 Feb 2026, 22:05:12
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────
[DEBUG 22:05:12] [XXX] After check: manual_recheck_active=False
* Check #1 completed for XXX ...

Timestamp:                              Sat 07 Feb 2026, 22:05:12
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────
[DEBUG 22:05:12] [XXX] UI Data Update: targets=['XXX']
[DEBUG 22:05:12] [XXX] UI Data Update: check_count=1
Target:                                 XXX
Last check:                             Sat 07 Feb 2026, 21:23:49
Next check:                             Sun 08 Feb 2026, 09:37:16 (in 11 hours, 32 minutes)
Check interval:                         11 hours, 32 minutes (Sat 07 Feb 10:33 - 22:05)

Timestamp:                              Sat 07 Feb 2026, 22:05:12
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Originally created by @tomballgithub on GitHub (Feb 8, 2026). Original GitHub issue: https://github.com/misiektoja/instagram_monitor/issues/64 I've had some debug statements in to see what's going on with BE HUMAN. My question is how is this intended to work, because "probability_for_cycle" returns "min(1.0, DAILY_HUMAN_HITS * sleep_seconds / day_seconds)" but I see it as always 1 (see below, it's calculating 28.836 for the min compare to 1) ``` debug_print(f"Probability Calculation: {DAILY_HUMAN_HITS * sleep_seconds / day_seconds}") debug_print(f"BeHuman: simulation start with probability {prob} for sleep_seconds of {sleep_seconds}") ``` I've noticed lately that I keep seeing BE HUMAN be the point at which my account gets flagged Maybe it's the 429 issue we've been observing ``` [DEBUG 22:05:12] [XXX] Check #1 completed **[DEBUG 22:05:12] [XXX] Probability Calculation: 28.836111111111112** **[DEBUG 22:05:12] [XXX] BeHuman: simulation start with probability 1.0 for sleep_seconds of 41524** [DEBUG 22:05:18] [XXX] BeHuman #1: explore feed peek OK [DEBUG 22:05:34] [XXX] BeHuman #2: viewed own profile OK [DEBUG 22:05:42] [XXX] BeHuman #3 error: cannot browse #grwm: 400 Bad Request - "fail" status, message "challenge_required" when accessing https://i.instagram.com/api/v1/tags/web_info/?__a=1&__d=dis&tag_name=grwm [DEBUG 22:06:12] [XXX] BeHuman #4: visited followee powhub OK [DEBUG 22:06:17] [XXX] BeHuman: simulation stop [DEBUG 22:06:17] [XXX] Sleeping 11 hours, 32 minutes for XXX, resumes at ~09:38:21 [DEBUG 22:06:17] [XXX] Next check scheduled for: Sun 08 Feb 2026, 09:37:16 [DEBUG 22:06:17] [XXX] UI Data Update: targets=['XXX'] ``` And here's what happened before it, no issues, even with fetching all those followings: ``` [DEBUG 21:23:49] [XXX] Fetching profile data from Instagram API... [DEBUG 21:24:01] [XXX] Profile loaded: followers=191, following=4435, posts=1 [DEBUG 21:24:01] [XXX] Story available: False [DEBUG 21:24:01] [XXX] UI Data Update: targets=['XXX'] * Followings number changed by user XXX from 4430 to 4435 (+5) [DEBUG 21:24:01] [XXX] Writing CSV entry to kara_elaine_long.csv: Type=Followings Count, Old=4430, New=4435 * Downloading Followings: 100%|████████████████████▉| 4434/4435 [11.3 names/req, reqs=393, mins=40.7, remain=0.1][DEBUG 22:04:44] [XXX] [close_pbar] ENTRY - thread_pbar is None: False * Downloading Followings: 100%|████████████████████▉| 4434/4435 [11.3 names/req, reqs=393, mins=40.7, remain=0.1] [DEBUG 22:04:44] [XXX] [close_pbar] logger_instance found: True, type: FilteredWriter [DEBUG 22:04:44] [XXX] [close_pbar] clean_final: * Downloading Followings: 99%|███████████████████░| 4,434/4,435 [11.3 names/req, reqs=393, mins=40.7, remain=0.1] [DEBUG 22:04:44] [XXX] [close_pbar] main_log is None [DEBUG 22:04:44] [XXX] [close_pbar] target: None, target_paths: ['XXX'] [DEBUG 22:04:44] [XXX] [close_pbar] No target, writing to all logs * Followers: reported (191) actual (191). Followings: reported (4435) actual (4434) * Followings (4435) actual (4434) saved to file 'instagram_XXX_followings.json' Added followings: XXX * Sending email notification to XXX * Webhook notification sent successfully Check interval: 10 hours, 11 minutes (Sat 07 Feb 11:54 - 22:05) Timestamp: Sat 07 Feb 2026, 22:05:12 ───────────────────────────────────────────────────────────────────────────────────────────────────────────────── [DEBUG 22:05:12] [XXX] After check: manual_recheck_active=False * Check #1 completed for XXX ... Timestamp: Sat 07 Feb 2026, 22:05:12 ───────────────────────────────────────────────────────────────────────────────────────────────────────────────── [DEBUG 22:05:12] [XXX] UI Data Update: targets=['XXX'] [DEBUG 22:05:12] [XXX] UI Data Update: check_count=1 Target: XXX Last check: Sat 07 Feb 2026, 21:23:49 Next check: Sun 08 Feb 2026, 09:37:16 (in 11 hours, 32 minutes) Check interval: 11 hours, 32 minutes (Sat 07 Feb 10:33 - 22:05) Timestamp: Sat 07 Feb 2026, 22:05:12 ───────────────────────────────────────────────────────────────────────────────────────────────────────────────── ```

kerem added the

bug

label

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

kerem commented

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

Author

Owner

@misiektoja commented on GitHub (Feb 11, 2026):

Yes, the calculations were not right when using hour range gating, I think it should be fixed now, small logical bug.

@misiektoja commented on GitHub (Feb 11, 2026): Yes, the calculations were not right when using hour range gating, I think it should be fixed now, small logical bug.

kerem commented

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

Author

Owner

@tomballgithub commented on GitHub (Feb 23, 2026):

I need to retest. I turned off BE_HUMAN because of 429s and accounts getting flagged.

I'll try a different account and check this.

@tomballgithub commented on GitHub (Feb 23, 2026): I need to retest. I turned off BE_HUMAN because of 429s and accounts getting flagged. I'll try a different account and check this.