Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

Smash Balloon Not Updating: Causes and How to Fix It

Smash Balloon Not Updating: Causes and How to Fix It

Short answer

Smash Balloon feeds stop updating when the plugin's feed cache is long, WP-Cron is not running, a page cache serves old HTML, or the social account connection has expired. Clear the feed cache first, then fix cron, page caching or the connection based on what changes.

Key takeaways

  • Smash Balloon refreshes feeds on a schedule, so short delays are normal.
  • Clearing the feed cache shows whether the automatic refresh is broken.
  • WP-Cron failures are the most common reason feeds never update on their own.
  • Page and CDN caches can keep serving an old feed even after Smash Balloon updates.
  • Expired account connections and API rate limits also block new posts.

Why is Smash Balloon not updating?

Smash Balloon feeds stop updating when the plugin's own feed cache is set too long, WP-Cron isn't running, a page cache keeps serving old HTML, the account connection has expired, or the platform's API is limiting requests.

Smash Balloon does not fetch new posts every time someone loads a page. It saves feed data and refreshes it on a schedule, which keeps your site fast and stays within each platform's API limits.

So a delay of a few hours can be normal. A feed stuck on the same posts for days is not.

This applies to all Smash Balloon feeds: Instagram, Facebook, YouTube, X (Twitter), TikTok and reviews. The settings names differ a little between plugins, but the causes are the same.

Smash Balloon's own article on feeds that won't update lists the official checks.

How often should a Smash Balloon feed update?

A feed should update on the schedule set in the plugin's caching settings, which is often every hour or a few hours, so new posts may take that long to appear.

Before you troubleshoot, compare the time of your latest post with the cache setting:

  • New post a few minutes ago. Wait for the next refresh, or clear the feed cache.
  • New post older than the refresh period. Something is blocking the update. Keep reading.

The cache time is a trade-off. Shorter times show new posts faster but make more API calls, which can run into rate limits on busy sites.

If you are setting up a feed from scratch, our guide on using the Smash Balloon Instagram feed covers the main settings.

How do you clear the Smash Balloon feed cache?

Open the Smash Balloon plugin's settings, find the caching options, and click the button to clear or refresh the feed cache; then reload the page that shows the feed.

General steps:

  1. In WordPress, open the Smash Balloon menu for the feed type, such as Instagram Feed or Facebook Feed.
  2. Go to the Settings screen.
  3. Look for the caching or feed cache section. In some versions it sits under an Advanced tab.
  4. Click the button to clear or refresh the cache.
  5. Open the page with the feed in a private browser window.

If the new posts now show, the feed works and only the schedule was the issue. If they only appear after you clear the cache by hand every time, the automatic refresh is broken.

Smash Balloon covers that exact symptom in its article on feeds that only update after clearing the cache.

Is WP-Cron failing to refresh the feed?

Yes, that is the most common cause; Smash Balloon refreshes feeds in the background with WP-Cron, and if scheduled tasks don't run, the feed never updates on its own.

WP-Cron is WordPress's built-in task scheduler. It only runs when someone visits the site, and hosts or plugins can disable it. WordPress explains how it works in its cron handbook.

Signs WP-Cron is broken:

  • Scheduled posts miss their time.
  • Other plugins' scheduled tasks, such as backups, stop running.
  • Tools > Site Health warns about scheduled events.

Fixes:

  • Check wp-config for DISABLE_WP_CRON. If it is set to true, make sure a real server cron job is calling wp-cron instead.
  • Set up a server cron job. Our guide on disabling WP-Cron and using a real cron job walks through it.
  • Look at the scheduled events list. Our guide on viewing WP-Cron events shows how to spot Smash Balloon's tasks.

For the deeper fixes, see WP-Cron not running.

Is a page cache serving an old copy of the feed?

If your cache plugin, host or CDN stores the whole page, visitors may see an old copy of the feed HTML even after Smash Balloon has new data.

This is very common on fast, heavily cached sites. Smash Balloon updates, but the saved page does not.

Fixes:

  • Purge the page cache for the page with the feed.
  • Shorten the cache lifetime for that page, or exclude it from caching.
  • Use AJAX loading if your Smash Balloon version offers an option to load the feed after the page loads. That lets cached pages still show fresh posts.
  • Purge the CDN if you use Cloudflare or a host CDN.

Our guide on clearing cache in WordPress covers each cache layer.

Our guide on clearing Cloudflare cache covers the CDN side.

SymptomLikely causeFirst fix
New posts appear after clearing Smash Balloon cacheWP-Cron not runningSet up a real cron job
New posts appear only after purging the page cachePage or CDN cacheExclude the page or use AJAX loading
Feed shows an error to adminsExpired account connectionReconnect the account
Updates work, then stop for a whileAPI rate limitsIncrease cache time
Only some feeds updatePer-feed settings or connectionCheck that feed's source account

Has the account connection expired?

Expired or revoked access tokens stop new posts loading, while the old cached posts keep showing; reconnect the account in Smash Balloon's settings to fix it.

Social platforms limit how long access lasts. Changing your password, removing app permissions or changing account type can also revoke access.

Steps:

  1. Open the Smash Balloon settings for that feed type.
  2. Look at the connected sources or accounts list for warnings.
  3. Remove the broken connection and connect the account again.
  4. Check that each feed still points to the reconnected source.

Smash Balloon shows error notices to logged-in admins on the page with the feed. Visitors do not see them, so log in and check.

Platforms also change which account types their APIs support. Instagram, for example, now requires a professional account for most API access, as the Instagram Platform documentation explains.

For Instagram-specific issues, see Smash Balloon Instagram feed not working.

For Facebook, see Smash Balloon Facebook feed not working.

Are API rate limits slowing updates?

Yes; each platform limits how many requests a site can make, so very short cache times or many feeds can hit the limit and pause updates for a while.

Signs of rate limiting:

  • Feeds update, then freeze for an hour or so.
  • Error notices mention rate limits or too many requests.
  • The problem gets worse when you add more feeds.

Fixes:

  • Raise the cache time to an hour or more.
  • Combine feeds where you can, so fewer requests are needed.
  • Avoid clearing the cache repeatedly while testing.

Smash Balloon describes slow-update causes in its article on feeds that update slowly or not at all.

Could a plugin conflict or old version stop updates?

Yes; an outdated Smash Balloon version, a security plugin blocking outgoing requests, or a script optimization plugin can all stop the feed refreshing.

Check these:

  • Update Smash Balloon. Platform APIs change, and old versions may stop working with them.
  • Outgoing requests. Firewalls or hosts can block calls to the social platform's API.
  • Script optimizers. Delayed or combined JavaScript can break AJAX loading.
  • Staging copies. A staging site with the same connection can use up rate limits.

To test for conflicts, use a staging copy, switch to a default theme, and turn off plugins one by one. Our guide on setting up a staging site explains how.

How do you keep Smash Balloon feeds updating reliably?

Use a real server cron job, keep the page with the feed lightly cached or loaded by AJAX, set a sensible cache time, and check the account connection every few months.

A simple routine:

  • Monthly. Look at each feed and confirm the newest post appears.
  • After password changes. Reconnect the social account.
  • After plugin updates. Clear the Smash Balloon cache and page cache.
  • After moving hosts. Check that cron still runs on the new server.

If you are not sure which Smash Balloon plugin does what, our explainer on what Smash Balloon is covers the product range.

The plugin's WordPress.org page also lists the changelog, which shows when fixes for API changes were released.

Frequently asked questions

How long does it take for new posts to show in Smash Balloon?

It depends on the cache time in the plugin's settings. New posts usually appear after the next scheduled refresh, which is often within an hour or a few hours. Clearing the feed cache shows them right away.

Why does my feed only update when I clear the cache?

The automatic background refresh is not running, which usually means WP-Cron is disabled or broken. Set up a real server cron job or fix WP-Cron, and the feed should refresh on its own again.

Can a cache plugin stop Smash Balloon from updating?

Yes. Page caches save the whole page, including the feed HTML. Visitors keep seeing that saved copy until the cache expires. Purge the page cache, exclude the page, or load the feed with AJAX.

Does Smash Balloon update the feed for visitors or only for admins?

Updates apply to everyone once the feed cache refreshes. Error messages about broken connections, though, only show to logged-in admins, so log in and visit the page to check for warnings.

Should I set the cache time as short as possible?

No. Very short cache times make more API requests and can trigger rate limits, which pauses updates entirely. An hour or a few hours is a good balance for most sites.

Sources

  1. My feed won't update Smash Balloon
  2. My feed does not update unless I manually clear the cache Smash Balloon
  3. My feed updates slowly or not at all Smash Balloon
  4. Cron WordPress Developer Resources
  5. Instagram Feed plugin WordPress.org
  6. Instagram Platform Meta for Developers

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.