Intermittent Cache Error

Hey Luke,

My guess would be that there is some sort of interaction with the caching plugin causing this.

We have an update coming out in a week or so that changes everything with the caching system. It will likely fix this issue. Otherwise you can try enabling the “Clear cache on interval” setting as this may also fix the issue.

– Craig

Sounds good. Looking forward to the update.

Yeah, I’ve got the ‘clear cache on interval’ turned on but it doesn’t seem to help.

The client mentioned that they have to update their social media passwords frequently (interns) so the token has to be reset more often than my other clients. Would that have any interaction?

Thanks!

I guess I’m not entirely sure though changing anything with the account could cause some cache somewhere to be incorrect I suppose.

Let me know if you have more questions in the meantime!

I’m running into a similar issue except re-installing/reconnecting doesn’t remove the error anymore.

Hey kohashi,

In that case, can you send me a link to the page that is having an issue? I can likely help you out then.

– Craig

brightestyoungthings.com, it is only showing the error on admin side. I am also now getting 429 errors on admin side only.

Hey again kohashi,

Typically when we see this error it means that either another plugin or “app” is making additional requests with your access token or your host/server is blocking requests to the Instagram API. The plugin caches your feed using a server-side request for security reasons and will attempt to use this instead of retrieving posts using the browser. If the server-side request is blocked it can cause 429 errors.

Can you see if your host is blocking access to the Instagram API?

So the host isn’t blocking them, I’ve been working with them trying to diagnose the issue (Pressable is the hosting company). Are the 429 and cache error are related based on what you’ve described? If the plugin is using the cache and trying to make a server side call instead for most requests. I’m logged in and it’s failing, so is it defaulting to browser request and that is getting the API blocked with 429s? They come and go, it’s not always erroring 429, but cache is definitely never working at the moment. Reconnecting the account does update what is in the cache though.

Actually it looks like the header is having a caching error from what I can tell. It seems to be responsible for burning out the access token.

We have an update coming out very soon (likely this week) that will fix this issue.

If you’d like, you can contact us on our website and get it immediately:

https://smashballoon.com/instagram-feed/support/

– Craig

Just wanted to say thank you, the new version seems to have taken care of this issue.

No problem! Let me know if you ever need anything else.

– Craig