Facebook Marketplace Alerts Not Working? Work Through This List

"Alerts not working" covers four genuinely different problems, and the fixes barely overlap. Work out which one you have before changing anything:

1. Nothing arrives at all. No notifications, no feed entries.
2. Notifications arrive late. You see them, but hours after the listing went up.
3. Alerts show items that already sold. Everything you message about is gone.
4. Alerts arrive, but they are junk. Accessories, parts, other buyers' wanted posts.

The first two are almost always delivery problems — phone settings, app settings, or no schedule. The third is a cadence problem. The fourth is a search-configuration problem and is covered in more detail in the negative keyword guide.

This order matters. Most people start by blaming the app and work backwards, which wastes an evening.

1. Notification permission. iOS asks once, and a reflexive dismissal is easy to forget. Settings → Notifications → the app. Confirm notifications are allowed and that the delivery style is not set to silent.

2. Focus modes. Work, Sleep and Driving focus modes withhold notifications from any app not on their allow list, and a Focus schedule can start applying without you changing a thing. This is the single most common cause of "it worked last week".

3. Low Power Mode. iOS defers background activity when the battery is low. Symptom: notifications arriving in a burst rather than as things happen.

4. Notification summary. Scheduled Summary batches non-urgent notifications into fixed delivery times. Useful for social apps, fatal for sourcing.

5. The app was force-quit. Repeatedly swiping an app away can affect how the system treats its background activity. Leave it in the app switcher.

6. Alerts disabled for that watchlist. Notification preferences are usually per-feature and sometimes per-search. If one search is silent and others are not, this is why.

7. The watchlist is paused. Paused searches do not scan, which produces exactly the same silence as a broken notification.

8. The scan is failing. A scan can fail for reasons that have nothing to do with you — a source being slow or temporarily unavailable. A tool worth using tells you when a scan last ran and whether it succeeded, so "found nothing" and "did not run" are distinguishable. If yours does not surface that, you cannot tell these two states apart, which is itself a problem.

Facebook's own Marketplace notifications are the common culprit here, and the honest framing is that they are not built for sourcing.

There is no interval to configure, no log of when the last check happened, and no way to distinguish "nothing was posted" from "nothing was checked". For someone buying a sofa eventually, that is fine. For someone trying to be first to message, it is unusable, because the one thing you need — a bound on the delay — does not exist.

A monitoring tool replaces that with a schedule. If it scans every 5 minutes, the worst case is that a listing is 5 minutes old when you hear about it. That is a real guarantee, and it is a different thing from being instant.

If every listing you message about has gone, nothing is broken — you are simply arriving after the category's window has closed.

How long listings survive varies enormously:

• Consoles, graphics cards, tool lots: frequently under an hour.
• Sneakers, bikes, cameras: hours to a day.
• Furniture, appliances, anything bulky: often days, because most buyers cannot transport them.

Match the interval to the category rather than to your budget. A daily scan is genuinely fine for furniture and genuinely useless for consoles. This is also the one symptom where upgrading to a faster tier is the correct fix rather than a workaround.

If scans are running and finding nothing, the search is too narrow. Loosen one constraint at a time — changing three at once tells you nothing about which one was the problem.

9. The price band is too tight. The most common culprit. A ceiling set from wishful thinking excludes everything real.

10. The radius is too small. Particularly outside major metros, where a 10-mile radius may contain very little inventory.

11. The keywords are too specific or misspelled. Search the way a seller would type it, not the way the manufacturer writes it. Add the spaced version, the unspaced version, and the common misspelling — underpriced listings are frequently underpriced precisely because they were misspelled and nobody else found them.

12. An exclusion word is removing everything. It happens: a word that seemed obviously bad turns out to appear in most legitimate listings in your category. If alerts dried up right after you added exclusions, remove the most recent ones first.

This is the opposite failure and it is more common than people admit, because it does not feel like a fault — it feels like the tool being annoying, and the response is to mute it.

The cause is almost always missing exclusion words. Accessory sellers put the product name in the title, parts sellers describe faults in the body text, and other buyers post "ISO" listings that read exactly like real ones.

The fix takes about two minutes: look at the last ten alerts you ignored rather than the ones you opened, find the word they have in common, and exclude it. Two or three rounds of that usually turns a feed you avoid into one you clear standing up.

A working setup has three properties, and it is worth checking yours against all three:

You can tell when it last ran. Without that, silence is ambiguous and you will keep re-checking manually, which defeats the point.

The alerts are worth opening. If you are skipping most of them, the exclusion list needs work — not the notification settings.

The cadence matches the category. Faster is not better in the abstract. It is better when listings disappear faster than your interval, and it is wasted money when they do not.

Get those three right and alerts become a two-minute habit rather than a background source of irritation.