In that case it seems like the ‘human behaviour’ is increasing the click rates or whatever IG is limiting? @JRVTeam
Does resolve the issue. Might be less than usual but still very present unfortunately
A new J update came out. 168 isnt fixed. Only thing is that it not gets registered in the error tab
Why would you have to go thru each account? Just copy the setting across all accounts.
Yes, you should be able to goto ‘copy settings’ at the bottom of advanced profiles. Select the accounts and settings you would like to transfer to the other accounts.
If you need help with it, lmk.
Fuck me for not knowing that! I just broke 2 fingers wide open having to hold CTRL + N …
Is anyone still getting constant 168 error codes for one of his accounts?
If yes, PM me so we can look more into it.
I’m not talking about the OOPs, please try again error.
yes! I’m not sure if, although it might have, disabling the human behaviour lowered it but still getting it a lot.
Could you explain why it’s basically timing out and how rate limits work? What could avoid it? Less actions and more resting times? if they only follow specific users, will the EB or API still somehow make underlying calls. It’s not like it’s keeping accounts from doing actions. It’s on and off for me at least.
Edit: The update is now showing the errors in read but that’s about it
Im unfollowing/following through EB using the human behavior and I have not yet received one error code. Not sure why its only affecting some accounts.
@tomsocial Without having to show your settings could you maybe say it you follow big bulks and longer wait times or just 1 every minute or something in between?
I’m running on DC proxies and barely getting blocks so the quality is good. Running about 2 slaves per proxy.
As mentioned before i’m not at 0 actions. I’m almost hitting limits however the error gets lifted on and off.
I let them scrape to extracted during their personal night time and perform EB follow actions during the active time.
I have got api scrape accounts that give sources to the EB accounts (api and EB accounts not getting error codes)
I do plus minus 15 actions with a delay of less than 150 seconds per operation and with a delay of plus minus 1 hour between operations (doing just around 100 actions a day for now) will increase the actions and shorten the delay between ops when I decide to increase the daily actions.
I hope this helps
Isnt the 168 the oops, try again error?
No, some users were getting it because they were using a different language than English.
Sometimes, it just gets stuck and then return the 168 timeout error.
Oh okay! In that case i’m still stuck on the 168 error related to the timeout show in red after the update @JRVTeam
PM me, and we will check it out.
I just got a 508 error when trying to follow a user on API?
Send am email to support and they will follow up with you.
@JRVTeam So i’m wondering, I let my accounts do actions during their active time through the EB and during their inactive time feed themselves with scraping users (send to own extracted users). Could I possibly avoid the 168 by putting the rank of the source of specific users at 1000 and the ones of the geo and friends of followers at both 1? This way it will only follow the specific users most of the time 1000 vs 1. But then i’m also wondering, how do they scrape during their inactive time? Do they automatically scrape from the geo and friends of followers even though they are at rank 1?
Thanks!