Why am I not getting any flight price alerts?

Usually because your alert can no longer fire, not because the fare never dropped. On Google Flights, Kayak or Skyscanner the alert is a saved search, so it inherits the dates you typed, the filters you ticked and a threshold the tool chose. The dates pass, the filters turn out to be unsatisfiable, or the alert fires so often you mute it. All three fail silently, which is the real problem. Flydar is built so none of them can: you describe a route and a trip length rather than a search, a window that has passed is flagged on your dashboard instead of pretending to watch, a filter tight enough to cost you deals warns you as you set it, and the judgement about whether a fare is low happens before any email is sent.

Can a flight price alert be too specific?

Yes, and it is the failure people least suspect, because an over-specified alert and a quiet route produce identical silence. Trip length is the usual culprit: fare rules carry minimum and maximum stay conditions, so a seven-nights-exactly trip and a six-to-nine-nights trip are separately priced products. Flydar takes trip length as a range rather than a number, and warns you at the moment you set one tight enough to cost you deals.

How do I stop getting so many flight price alert emails?

The volume comes from the trigger. Most free tracking fires on any significant change in either direction, including increases, so muting it is the rational response and also the end of its usefulness. Flydar's trigger is different: a fare has to fall clearly below what that route normally costs before anything is sent, so rising prices and sales over ordinary fares never reach you.

Does no alert mean the price never dropped?

Not on its own, and a free alert cannot tell you which it is. Pull a flexible-date calendar for the route by hand once. If fares in the grid are visibly moving while your inbox has been quiet for months, the alert is the problem rather than the route.

Why your flight price alerts never go off

Q: Do flight price alerts expire?

A per-search alert stops meaning anything once the dates you searched have passed, and nothing notifies you when that happens. Google's help page for tracked flights documents how to add and remove tracking but no expiry event, because from the product's side nothing expired. The saved search still exists. It has just stopped describing a trip anyone can take. Flydar handles this the other way: a rolling window never passes at all, and a fixed one that does is flagged amber on your dashboard as 'Dates passed' with a prompt to update it, so a tracker never sits there looking active while doing nothing.

Your Google Flights alert has been silent since March. Or your Kayak one, or Skyscanner’s. You have drawn the obvious conclusion: the fare never dropped.

The likelier answer is that it lost the ability to fire months ago and nothing told you, because a free alert reports success and failure the same way. It produces nothing.

There are four causes. Three of them are not bugs, they are consequences of what a free alert is underneath: a saved search. Toggle tracking on Google Flights and the thing being watched is the query you ran, so it inherits the dates you typed, the filters you ticked, and a threshold the tool picked for you. Each was a guess about a trip you had not planned yet. Each is a separate way to go quiet.

Flydar is built the other way round. Cause 3 cannot happen to it at all, causes 1 and 2 cannot happen without it telling you, and cause 4 happens to everybody. That is not a coincidence, it is the reason it exists, so each cause below says plainly what happens on a per-search alert and what happens on a route watcher instead.

1. The dates you set have already gone by

You looked at the 14th to the 22nd of March, toggled tracking, and something has been faithfully monitoring a trip that departed five months ago.

Nothing announces this. Google’s help page for tracked flights covers how to add tracking, how to remove it, and how to switch notifications on and off (Track flights and prices). It documents no expiry event, because from the product’s side nothing expired. The saved search still exists. It has just stopped describing a trip anyone can take.

Rebuilding it only restarts the clock: new dates, same silent death a few months on, nothing to remind you. Most people find out when they finally go to book.

On Flydar the silent part cannot happen. Two things stop it. Most windows are relative to today, a rolling span that moves forward as time does, so there is nothing to pass and nothing to renew. And if you do pin a fixed window, because sometimes you know the trip has to be in April, that window can end like any other.

The difference is what happens when it does. The tracker does not sit in your dashboard wearing a “watching” badge while quietly doing nothing. It turns amber, the status reads Dates passed, and a line under the route tells you these dates have passed and offers to update them so it keeps watching. One click and it is live again.

That is the actual grievance in this section. Not that dates exist, but that nothing told you when they stopped mattering. If you would rather never think about it, set the window wide and leave it.

2. Your filters describe a trip almost nothing satisfies

Every constraint multiplies against you. Nonstop only, one airport rather than the whole metro area, a fixed departure time, a target price: four filters that each halve the field leave a sixteenth of the fares that could have reached you. None feels unreasonable alone.

Trip length is the one that catches people, because it does not feel like a filter at all. Fare rules have carried minimum and maximum stay conditions for decades, which is why the same route on the same departure date prices differently for a five-night trip than a nine-night one. “Exactly seven nights” and “six to nine nights” are two different requests, and the first is far harder to satisfy.

What turns that from a mistake into a trap: nothing checks whether the specification you built can be satisfied. You tick the boxes, the alert accepts them, and the result is silence identical to a quiet route. Months later you cannot tell “no fare qualified” from “no fare was cheap,” and neither can the tool.

On Flydar the trap is closed at both ends. Trip length goes in as a range because that is how a trip exists in your head before it exists on a calendar. Pick a city rather than an airport and every airport in it is included, both ends, without you managing six searches. And if you do set a range tight enough to cost you deals, the field says so on the spot: a tight trip length matches fewer deals, and you will still get alerts, just less often. It does not block you, because wanting a specific trip length is legitimate. It warns you, because setting the filter is the last moment anyone can. After that there is only silence, and silence cannot be annotated.

3. It went off constantly and you dealt with it

Rule this one out early, because it hides in plain sight.

The default trigger on most free tracking is a significant change in either direction. Google’s documentation lists, among the notifications you can receive, that prices for a route you track are likely to go up. Reasonable to send if you are timing a purchase you have already committed to. Over a few weeks it is also how a sender gets muted or an inbox rule gets written.

That is not a broken alert. That is a working alert you have trained yourself to ignore.

The outcome is identical either way: a fare drops, an email arrives, you do not read it. The threshold was never yours. It was set to “something happened” rather than “something worth acting on happened,” and no care on your end changes what a tool decides is worth sending.

On Flydar the threshold is not a setting, it is the product. A fare has to fall clearly below what that route normally costs before anything is sent. A price rising sends nothing. A sale banner over an ordinary fare sends nothing. The research you would otherwise have to do on every notification, working out whether this number is good for this route, has already happened by the time the email exists. That is why there is something worth opening when one arrives, and it is the argument the hub piece on whether alerts are worth it works through at length.

4. The route really is flat

The one case where the silence is honest, and the least common of the four.

Some routes sit in a narrow band: a single carrier, a slot-constrained airport, one departure a day. The price steps rather than swings and can sit still for a month. A competitive short-haul with a low-cost operator behaves nothing like this, and you cannot tell which you have without ten minutes and a calendar grid (the method is here).

On Flydar nothing changes here, and no honest tool would claim otherwise. A flat route is doing nothing. Watching it costs you no attention, which is worth something, but nobody invents a drop that is not there.

The four causes, side by side

The cause	Free per-search alert	Flydar
1. Dates have passed	Dies silently; rebuild it and the clock restarts	A rolling window never passes; a fixed one that does turns amber and asks to be updated
2. Filters too narrow	Accepted without a check, then silence you cannot read	Trip length is a range, a city means every airport, and a tight filter warns you
3. Fires on any change	Threshold is “something happened,” so you mute it	A fare must fall clearly below the route’s normal price
4. Route is flat	Correct silence	Correct silence

None of the first three can happen without you being told, which is the whole difference between a quiet tool and a dead one.

The five-minute diagnosis

Read the dates on every alert you have running. Anything in the past is cause 1, decorative since the day it passed.
Search your mail by sender. A pile of unread tracking emails is cause 3.
Rerun the route by hand with your filters off. Fares in the grid and nothing in your inbox is cause 2.
Look at the spread in that grid. A whole month within a few percent of itself is cause 4.

Anything but a 4 and your tool is the problem, not your route.

When paying for this is the wrong call

Three cases. Booking inside the next week or two: there is no watching period left to sell you, the cheap buckets are usually gone, and the direction of travel is upward. A cabin above economy: Flydar tracks economy, so this is not a close call. A cause 4 diagnosis: save your money and check back in a season.

The short version

If your alert has been quiet for months, the burden of proof is not on the route. It is on the alert. Three of the four reasons it goes silent are things you were made to guess at before you had any way to guess well, and then made to maintain forever without being told when a guess went stale.

You can keep rebuilding them every few months and hope you notice when one stops working. Or you can describe the route in a sentence and let the tool be the one that keeps track of whether it still makes sense, which is what Flydar is.

Either way, run the four checks first. If the answer comes back as a flat route, keep your money and look again in a season. If it comes back as any of the other three, there is a better question than why the alert never went off: how many months did it sit in your account looking like it was working?