The alerts log
How the alerts log records every notification the system has sent, from overdue flights to expiries and re-evaluation blocks, so nothing is silently missed.
Last reviewed
FlyerOS raises alerts as the day runs: a flight that is overdue back, a booking that stopped being valid, a document about to expire, a nudge worth sending. The alerts log is the record of every one of them, so an alert that mattered is never just a notification someone happened not to see.
What it records
Every notification the system has sent, with what it was about and when. Overdue flights, re-evaluation blocks where a booking stopped meeting the rules, expiries coming up, and the nudges that went out. It is one place to see everything the system flagged, rather than piecing it together from people's memories.
Why a log and not just a notification
A notification is easy to miss. It arrives, it is glanced at, it scrolls away. The log means the alert still exists after the moment passed, so you can go back and check whether the overdue flight was chased, whether the expiry was handled, whether the block was resolved or worked around.
Using it during the day
The duty team uses the log to make sure nothing fell through: the flight that was overdue and is now back, the block that was cleared, the expiry that was renewed. At the end of a busy day it is the answer to "did we deal with everything that came up," rather than a hopeful yes.
Re-evaluation blocks
When a booking stops meeting the rules after it was made, because a medical lapsed or an aircraft went unserviceable, FlyerOS re-evaluates and flags it. Those blocks land in the log too, so a booking that quietly became invalid does not slip through to the day it was due to fly.