jarvee not reaching follow limit

neoxdz

Junior Member
Joined
Mar 15, 2017
Messages
185
Reaction score
46
Hello guys,
I have an issues with jarvee right now, 50% of the accounts aren't finishing following, for example i have accounts that should follow 500 people per day, yet at the end of the day , i can clearly see that they only followed like 200 or 100 people, anyone experience this before?
 
Maybe you set up the timing and wait more between actions and when starts to like it doesn't have the time to reach the daily number. Or, if you have slower proxies it can slow the process = lower number of follows. Or, your pc/VPS can't keep up with the requirements of Jarvee and will process slower the actions. Or, it doesn't find the right targets to follow which you programmed for sourcing. It can be multiple reasons.
 
Proxies, too strict filters (leading to timeout), sources, blocks.

These are the potential reasons. Try fix each one until you hit the limits!
 
i'm gonna change the filters , I also have follow different users across all accs but i don't think that's what's causing me that, i don't think it's the proxies they're HQ IPV4 and they're fast, gonna update you guys if i find the cause,
what's interesting is that some accs do hit the limit while others don't.
 
It can be one of those two options:
1. Your actions getting blocked after 150-200 Actions executed - Consider changing your proxy.
2. Following 500 a day is a bit too much. I suggest you to follow at least 350 a day.
3. Make sure to check your timers - if not configured to execute 24/7 it can split your actions 50% / 50 in a period of 24 hours
 
Which proxy are you using?
upload_2019-3-13_23-44-8.png

how is that?
 
Double check your filters also add new sources, they run out pretty fast
Also a good proxy should have a speed less 2000ms, aim for 1000, when buying proxies consider proxy location
I do 1k follows/day so you arent doing too much
Another problem is if you have lot of accounts on a single ip insta tends to slow your requests, make you wait, fail to load content intentionally
I highly believe your problem is adding new sources
 
Back
Top