Docs    Twitter    Troubleshooting

My feed won’t show the latest tweets

Why an X (Twitter) feed does not show the newest posts, usually a caching setting set too high in the plugin, the server or another plugin.

Is your feed missing your latest Tweets?

In this guide, we’ll walk you through a quick check and the most common causes, with how to spot each one and how to fix it. All you need is access to your WordPress dashboard.

Before you get started, make sure the latest version of Custom Twitter Feeds is installed and activated on your WordPress site.

Clearing the Feed Cache

Your feed shows a saved copy of your Tweets that the plugin updates in the background on a schedule. A new Tweet appears on your site after the next update.

Clearing the cache runs an update right away. This is the fastest way to find out whether your feed is just waiting.

To get started, we’ll clear the cache from the plugin settings. First, go to Twitter Feed » Settings in your WordPress dashboard. Then click the Feeds tab.

The Twitter Feed Settings menu item in the WordPress dashboard and the Feeds tab of the Settings page

Next, click Clear All Caches, directly under the Caching list.

The Caching setting on the Feeds tab with an arrow pointing to the Clear All Caches button

Each click uses one cache credit. The line below the button shows how many credits you have left and when they reset. The count changes after you reload the page.

Now open the page with your feed in a private browser window, so you see a fresh copy of the page.

If your latest Tweets appear, your feed was waiting for its next update. Continue with Shortening the Caching Interval below. If they don’t appear, work through the rest of the sections in order.

Shortening the Caching Interval

How to Tell

Your latest Tweets appeared after you cleared the cache.

How to Fix It

The plugin updates your feed in the background every 2, 12, or 24 hours. A shorter interval brings in new Tweets sooner.

On the same Feeds tab, open the Caching list and choose Every 2 hours.

The Caching list on the Feeds tab set to Every 2 hours

When done, click Save Changes.

The bottom of the Feeds tab with an arrow pointing to the Save Changes button

Your feed is now set to update every 2 hours, within your site’s daily update limit. If new Tweets still take longer than that to appear, continue with the next section.

Adjusting Your Caching Plugin

How to Tell

Your site uses a caching plugin. Your latest Tweets appear right after you clear that plugin’s cache.

How to Fix It

Custom Twitter Feeds works with most caching plugins. A caching plugin keeps its own copy of your page. New Tweets appear only after that copy is refreshed.

In your caching plugin’s settings, set it to skip the page with your feed or to clear its cache more often.

If you use W3 Total Cache, you can also turn off Page Cache or Object Cache to see whether that brings in your latest Tweets. For Page Cache, go to Performance » General Settings and uncheck Enable in the Page Cache section.

The Performance General Settings menu item in the WordPress dashboard and the Enable checkbox in the Page Cache section of W3 Total Cache, unchecked

For Object Cache, scroll down to the Object Cache section and uncheck Enable.

The Enable checkbox in the Object Cache section of W3 Total Cache, unchecked

When done, click Save Settings at the top of the page.

The W3 Total Cache General Settings page with an arrow pointing to the Save Settings button

Now check your feed again. If your latest Tweets appear after turning off a cache, your caching plugin was the cause. You can turn that cache back on and set the plugin to skip the page with your feed or to clear its cache more often.

If your latest Tweets still don’t appear, continue with the next section.

Checking Your Web Host’s Caching

How to Tell

Your site is on a managed WordPress host, such as WP Engine. Your feed stays behind even after you clear the feed cache and any caching plugin.

How to Fix It

Many managed WordPress hosts run their own caching system on their servers. Contact your host and ask them to exclude the page with your feed from their caching or to clear it more often.

Once your host has made that change, check your feed again. If your latest Tweets still don’t appear, continue with the next section.

Checking Your Daily Update Limit

How to Tell

Your feeds use many sources. Each source updates less often than the interval you chose.

To see your limit, look below the Caching list on the Feeds tab. The green note there shows how many source updates your site receives each day.

The Caching setting on the Feeds tab with an arrow pointing to the note that shows the daily source updates for the site

The number depends on your license level. It is 12 on the basic license level, 18 on the plus license level, and 24 on the elite license level.

The limit applies per site. Every source on every feed shares it. For example, with 12 updates a day and 24 sources, each source updates about once every other day.

How to Fix It

Remove any feeds or sources you no longer use. Your updates then go to the ones you display. If you need more updates, you can upgrade to a higher license level.

Our guide on the changes to the Twitter API covers these limits in more detail.

Note: On the free version, your feed updates once a week. To update your feed more often, you can upgrade to a paid license level.

Once your updates are in order, check your feed again. If it still doesn’t update on its own, continue with the next section.

Making Sure WP-Cron Is Running

How to Tell

Clearing the cache brings in your latest Tweets. Your feed doesn’t update on its own, even after your interval has passed and your site has updates left.

How to Fix It

The plugin’s background updates run through WP-Cron, the WordPress task scheduler. On some servers, WP-Cron is turned off. Those updates then never start.

To get them running, follow our guide on the cron jobs workaround. Then check your feed again. If it still doesn’t update on its own, continue with the next section.

Turning On Force Cache

How to Tell

You’ve worked through the sections above. Your feed still doesn’t update on its own.

How to Fix It

The plugin has one more caching setting to check. First, go to Twitter Feed » Settings and click the Advanced tab.

The Settings page with an arrow pointing to the Advanced tab

Then, scroll down and turn on Force Cache to clear on interval. This setting is on by default. You only need to change it if it was turned off on your site.

The Force Cache to clear on interval setting on the Advanced tab, turned on

When done, click Save Changes.

The Advanced tab with an arrow pointing to the Save Changes button at the bottom of the page

Your settings are now saved. If your feed still isn’t showing your latest Tweets, continue with the next section.

Still Not Working?

If your feed still isn’t showing your latest Tweets, our team can take a closer look. Contact our support team and include these details:

  • The URL of the page with your feed
  • The feed type and the source that isn’t updating
  • The fixes from this guide that you’ve already tried
  • Your System Info

That’s it! You now know how to find out why your feed isn’t showing your latest Tweets and how to fix it. Next, check out our guide on the changes to the Twitter API to learn how feed updates work.

Frequently Asked Questions

Below, we’ve answered some of the most common questions about feeds that don’t show the latest Tweets.

Can my feed update each time the page loads?

Your feed updates in the background on a schedule rather than on each page load. See Shortening the Caching Interval above for the intervals you can choose.

What are cache credits?

Cache credits are what the Clear All Caches button uses, one credit per click. See Clearing the Feed Cache above for where to find how many you have left.

Does Custom Twitter Feeds work with W3 Total Cache and other caching plugins?

Yes, it works with most caching plugins. If your feed isn’t updating, see Adjusting Your Caching Plugin above for the settings to change.

support

Couldn’t find your answer in the docs?

Contact Support