Scraping with JV cause Temporary blocks / EV of course.
Scrape data for perform actions of master accouts up to 100 calls per hour - ok for me.
When I want scrape any data here comes hell.
U mean master account ok to scrape 100 api per hour To perform actions ?
I’ve got these recommendations from Jarvee’s support regarding Scraper account’s API calls limits
Maybe that helps as well. Cheers
1 Like
Good luck…With 50 per hour if you use any filters.
1 Like
I think mostly it’s due to Jarvee problem as maybe IG did something on their side and they are able to detect Jarvee … I did a test same proxies and accounts with different a bot… The one without Jarvee is able to do action while Jarvee can’t lol
1 Like
I think IG can detect JV because when solving temporarily locked accounts IG says that we noticed unusual activity hence logged us out and locked the accounts. JV needs to accept it and work on it. Maybe they secretly know that they are being detected but they don’t want to accept is because they are working on a solution.
Well said bro 
Good luck with 1-2 api errors as well - a few minutes after setting up the scraper you can already forget it for that day 
Seriously, when we lower the api errors/calls so heavily, soon we would need 10 scrapers for 1 main if we want to use the very basic filtration to get targeted results. Otherwise we would need to lower the filters to a point where we can just do it on the main account itself, without using scrapers.
The reason why I’m still in the scraper warzone is exclusively the ability to use “remove poor quality sources” and “favour sources with high follow back ratio”. Otherwise I would immediately start using an external scraper and follow from the specific users.
2 Likes
I don’t think Jarvee is fully detectable, but I just lost 30 child accounts today. So I am thinking somewhere down the line there is a fingerprint, because there is no reason why they are getting banned on my behalf. I know what I’m doing and it’s been working this way for a while 
If you lose many accounts in 1 day than probably Instagram was able to connect the accounts with each other.
yes not fully detectable but they are connecting the dots. Like accounts with rambler connect them all and it does not matter the type of proxies you are using. They are keeping all those accounts in the same basket and banning them if they find something unusual with those accounts like api calls or actions. One red flag and those accounts are gone. It is a combined issue of JV and accounts creation. this is my opinion, you are entitled to have different opinion.
2 Likes
Jarvee needs to step its game up or people are just gonna leave…
2 Likes
i like how when major crisis like this happens JV support is nowhere to be found in this forum
1 Like
I’m fine with that. They still respond to queries via their program and I’m sure they are busy fixing the issue.
i mean… all they tell u is too change your proxies and set api limits. nothing helpful
Current method isn’t sustainable.
Wow. So much negativity.
Did someone tell you that this the Jarvee support forum?
There are 2 kinds of people. Ones that make a nice living with this software, and people who fill this thread with negative comments.
I am here already for some years. And from what I understand you have to email for support. That is already so for years and years.
2 Likes
If you think there’s just two types of people, you world is pretty binary.
Everyone on this thread are complaining and they have the right to. Software is not working. what else do you expect? you want people to keep paying money for JV and wasting more on proxies and vps at the same time?
The software works fine. Why do you think the software is to blame when IG limits API calls or asks for EV’s ?
I wrote my own IG bot, for some specific tasks. I also help someone who uses different software. The same problems mentioned in this thread I see there too. It is not a Jarvee problem.