Outbox bug report

Hi Mohammad Ali,

Thanks for the detailed report, and for separating the two issues so clearly. Let me take them one at a time.

**1. Bulk delete leaves messages showing**

Your observation is a strong clue: the messages really are deleted on the server (that is why deleting them again individually says they no longer exist), but the list on screen is not refreshing to show it. So the delete works; the display is stale, exactly as you suspected.

The usual cause is a caching layer serving an old copy of the list. Could you check a few things:

– After a bulk delete, do a hard refresh (Ctrl+F5, or Cmd+Shift+R on Mac). Do the rows disappear then?
– Any caching or performance plugin active (WP Rocket, LiteSpeed, W3 Total Cache), or object cache (Redis)?
– Were you on page 2 or later, or using a filter or search, when it happened?
– Any errors in the browser console (F12, Console tab) when you click Delete Selected?

**2. Resend does nothing**

One setting can cause this quietly. If a recipient number is outside your allowed countries under **Gateway → Country Restrictions**, Resend is blocked and will not send. That often applies to exactly the messages that failed the first time. A short notice should appear near the top of the screen, but it is easy to miss.

Could you confirm:

– Do you have any Country Restrictions set under Gateway?
– On Resend, do you see any brief message pop up, or truly nothing?
– Which WSMS version (it should be 7.2.6) and which SMS gateway are you using?

With those answers we can pinpoint both, and if it is a bug on our side we will get it fixed in the next release.

Best

Hi Mohammad,

Thanks for the extra detail, that pins it down.

On the bulk delete: the messages are genuinely removed from the database. What comes back after a reload is a cached copy of the list. The Outbox loads its data through the WordPress REST API, and LiteSpeed Cache caches REST API responses by default.

To confirm it, deactivate LiteSpeed Cache for a moment, delete a few messages, then reload the Outbox page. If the rows stay gone, the cache is the cause.

To fix it for good, do one of these and then purge all caches:

– Turn off “Cache REST API” in **LiteSpeed Cache → Cache → Cache**
– Or keep it on and add /wp-json/wpsms/ to “Do Not Cache URIs” in **LiteSpeed Cache → Cache → Excludes**

On Resend: what you described is how it works today. Resend sends the message again, and every send is logged as its own Outbox record, so the original row stays as history and the new attempt shows up with its own status.

That said, your point is fair. A row that shows Pending and then turns into Sent would read much better than a second row appearing out of nowhere. I have noted it as an improvement for a future release. If you would like to follow it, you are welcome to open it here: https://github.com/wp-sms/wp-sms/issues/new

Best