# New Update Problem (Sources)

**URL:** <https://mpsocial.com/t/new-update-problem-sources/83439>\
**Category:** Instagram Marketing\
**Created:** [September 9, 2019, 6:04am UTC](https://mpsocial.com/t/new-update-problem-sources/83439 "2019-09-09T06:04:06Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![testing123](https://mpsocial.com/user_avatar/mpsocial.com/testing123/32/36790_2.png) [@testing123](https://mpsocial.com/u/testing123)\
**Post date:** [September 9, 2019, 6:04am UTC](https://mpsocial.com/t/new-update-problem-sources/83439/1 "2019-09-09T06:04:06Z")

</div>

Hey guys, new update from J, wondering if anyone experience similar problems?

Everything working fine but after the update, Ive been getting “no more results found” on ALL accounts.  
Some have over 140 sources which makes no sense. Filters are also very moderate too. I’m trying to test our old forum threads on this sources issue, but wondering if anyone is getting after the 8th?

Anyone else get this issue as well, thanks?

---

<div class="post-metadata">

**Author:** ![Kgnkr](https://mpsocial.com/user_avatar/mpsocial.com/kgnkr/32/35741_2.png) [@Kgnkr](https://mpsocial.com/u/Kgnkr)\
**Post date:** [September 9, 2019, 6:27am UTC](https://mpsocial.com/t/new-update-problem-sources/83439/2 "2019-09-09T06:27:09Z")

</div>

Getting the same error

---

<div class="post-metadata">

**Author:** ![testing123](https://mpsocial.com/user_avatar/mpsocial.com/testing123/32/36790_2.png) [@testing123](https://mpsocial.com/u/testing123)\
**Post date:** [September 9, 2019, 6:29am UTC](https://mpsocial.com/t/new-update-problem-sources/83439/3 "2019-09-09T06:29:10Z")

</div>

Sorry found out - I enabled ONLY USE EMBEDDED in profiles. Scraping needs api, I turned off the ONLY and everything is working fine again. Guess if it aint broke dont fix it. Hope this helps!

---

<div class="post-metadata">

**Author:** ![Drav](https://mpsocial.com/user_avatar/mpsocial.com/drav/32/35148_2.png) [@Drav](https://mpsocial.com/u/Drav)\
**Post date:** [September 9, 2019, 6:29am UTC](https://mpsocial.com/t/new-update-problem-sources/83439/4 "2019-09-09T06:29:50Z")

</div>

Probably need to relogin API.

 ![20190908_130115](https://mpsocial.com/uploads/default/original/3X/6/0/60cced6e2795ee947939f782326d29d1ee64df00.jpeg)

---

<div class="post-metadata">

**Author:** ![Typhoon](https://mpsocial.com/user_avatar/mpsocial.com/typhoon/32/32538_2.png) [@Typhoon](https://mpsocial.com/u/Typhoon)\
**Post date:** [September 9, 2019, 6:43am UTC](https://mpsocial.com/t/new-update-problem-sources/83439/5 "2019-09-09T06:43:56Z")

</div>

[SOLUTION]

Be sure to unchecked this option. So now you can scrape via api but do all’ the action via EB (if you have enabled it).

![Immagine](https://mpsocial.com/uploads/default/original/3X/1/b/1b26c24a9ccc2b0dceba4cfede5f6d1247b9f64f.png)

---

<div class="post-metadata">

**Author:** ![Tyson](https://mpsocial.com/letter_avatar_proxy/v4/letter/t/b4bc9f/32.png) [@Tyson](https://mpsocial.com/u/Tyson)\
**Post date:** [September 9, 2019, 7:19am UTC](https://mpsocial.com/t/new-update-problem-sources/83439/6 "2019-09-09T07:19:27Z")

</div>

Anyone know how to get the only use eb (do not use api) function to work properly? It says it will auto select other account that’s login to api to do the scraping. But how does that work?

---

<div class="post-metadata">

**Author:** ![ciras](https://mpsocial.com/user_avatar/mpsocial.com/ciras/32/27687_2.png) [@ciras](https://mpsocial.com/u/ciras)\
**Post date:** [September 9, 2019, 7:48am UTC](https://mpsocial.com/t/new-update-problem-sources/83439/7 "2019-09-09T07:48:04Z")

</div>

Hey scrapers and let them get Specify users to follow.

---

<div class="post-metadata">

**Author:** ![samsam09](https://mpsocial.com/user_avatar/mpsocial.com/samsam09/32/37059_2.png) [@samsam09](https://mpsocial.com/u/samsam09)\
**Post date:** [September 9, 2019, 2:43pm UTC](https://mpsocial.com/t/new-update-problem-sources/83439/8 "2019-09-09T14:43:33Z")

</div>

If you only use the EB a lot of tools and functionality won’t work

---

<div class="post-metadata">

**Author:** ![Drav](https://mpsocial.com/user_avatar/mpsocial.com/drav/32/35148_2.png) [@Drav](https://mpsocial.com/u/Drav)\
**Post date:** [September 9, 2019, 3:17pm UTC](https://mpsocial.com/t/new-update-problem-sources/83439/9 "2019-09-09T15:17:18Z")

</div>

I think it picks a random account.

---

<div class="post-metadata">

**Author:** ![Tyson](https://mpsocial.com/letter_avatar_proxy/v4/letter/t/b4bc9f/32.png) [@Tyson](https://mpsocial.com/u/Tyson)\
**Post date:** [September 9, 2019, 4:10pm UTC](https://mpsocial.com/t/new-update-problem-sources/83439/10 "2019-09-09T16:10:27Z")

</div>

How about the follow source? Do I just need to set the follow source in the main account? Thanks

---

<div class="post-metadata">

**Author:** ![Drav](https://mpsocial.com/user_avatar/mpsocial.com/drav/32/35148_2.png) [@Drav](https://mpsocial.com/u/Drav)\
**Post date:** [September 9, 2019, 5:03pm UTC](https://mpsocial.com/t/new-update-problem-sources/83439/11 "2019-09-09T17:03:44Z")

</div>

Correct 👍👍👍👍👍👍

---

<div class="post-metadata">

**Author:** ![embraceone](https://mpsocial.com/user_avatar/mpsocial.com/embraceone/32/34092_2.png) [@embraceone](https://mpsocial.com/u/embraceone)\
**Post date:** [September 9, 2019, 5:10pm UTC](https://mpsocial.com/t/new-update-problem-sources/83439/12 "2019-09-09T17:10:38Z")

</div>

It shouldn’t be made possible to check two options which effectively cancel each other out. Jarvee needs to sort out issues like these.

---

<div class="post-metadata">

**Author:** ![maw101](https://mpsocial.com/letter_avatar_proxy/v4/letter/m/82dd89/32.png) [@maw101](https://mpsocial.com/u/maw101)\
**Post date:** [September 10, 2019, 7:55am UTC](https://mpsocial.com/t/new-update-problem-sources/83439/13 "2019-09-10T07:55:14Z")

</div>

Agreed. JV is in a bit of a state of flux at the moment - lots of updates coming out with features put in fairly hurriedly to try to give us a working solution, but not necessarily fully thought through.

It’s a difficult time to try to confirm what is and isn’t working!

Hopefully a more complete update will come soon with the process fully mapped out and working.
