A flight on a trip is showing stale times or no live status. In rough order of likelihood:
1. It's not in the live window yet
Live tracking starts automatically about a day before departure. A flight next month showing only its scheduled times is behaving normally; there's no live data to show yet. See Live flight tracking.
Fix: nothing needed. It goes live as departure approaches.
2. The data feed has a gap
Live coverage varies by airline, airport, and region. Small regional carriers and remote airports can go quiet for stretches, and some airlines don't publish gate or actual-time data at all.
Fix: open the flight, tap ⋯ beside Edit, and choose Check for updates to force a fresh lookup. If it's greyed out with a countdown, it was checked recently; there's a short cooldown per flight. If the check comes back with nothing new, the feed genuinely has nothing newer.
3. The flight details don't match the airline's
Live data is matched on airline code, flight number, and date. A mistyped flight number, the marketing carrier instead of the operating one (codeshares), or a wrong date means lookups find nothing, or the wrong flight.
Fix: open the flight, check the airline code and number against the booking confirmation, correct, then refresh.
4. The trip is muted (signals only)
Muting a trip silences its signals: no delay or gate-change notifications. The flight's on-screen status still updates. If the complaint is "no notifications" rather than "stale screen", check the trip's notification menu (the gear and bell above the itinerary).
Fix: set the trip's notification menu to In-app or Email and in-app, and confirm the flight signal kinds are enabled in Settings → Signals. See also Push notifications aren't arriving.
About "Est." arrivals
An arrival labelled Est. means the data feed went quiet before landing was confirmed, so an on-schedule arrival was assumed rather than leaving the flight airborne forever. A manual refresh replaces it with real data when available.