System Setup – Flight Change Queue
Overview
The Flight Change Configuration section lets admins define thresholds and notifications for flight schedule changes.
The system classifies changes as Tiny, Small, or Large. It can also send alerts and trigger extra warnings close to departure.
Purpose
Use this configuration to:
Categorize flight schedule changes by duration.
Notify designated staff when changes occur.
Define a timeframe for warnings before flight departure.
Standardized thresholds reduce manual checks and missed changes.
Fields and options
Each change category (Tiny/Small/Large) has its own Earlier and Later threshold. Thresholds are in minutes.
1. Earlier (minutes)
Defines how many minutes earlier a flight can move and still be classified in each category.
Example:
Tiny: 10 minutes earlier
Small: 20 minutes earlier
Large: 60 minutes earlier
2. Later (minutes)
Defines how many minutes later a flight can move and still be classified in each category.
Example:
Tiny: 20 minutes later
Small: 30 minutes later
Large: 70 minutes later
3. Warning – Email
The email address that receives flight change alerts.
Enter a shared inbox if possible (for example operations or customer service).
4. Warning – Before Departure (hours)
Defines how close to departure the system should apply the “before departure” warning logic.
Example: 5 means “within 5 hours of departure”.
Instructions for Configuration
Go to Setup → System Setup → Flight Change Queue → Flight Change Configuration.
Set Earlier and Later thresholds for Tiny, Small, and Large.
Example: If Tiny is up to 10 minutes earlier, then 15 minutes earlier becomes Small.
Enter the Warning – Email recipient.
Set Warning – Before Departure (hours).
Save.
Once saved, the system will automatically classify flight time changes and notify the specified contact by email.
Troubleshooting Guide
1. Not receiving flight change emails
Cause: Incorrect or inactive email address entered.
Solution: Verify the address and confirm the inbox can receive system emails.
2. Flight changes are not classified correctly
Cause: Incorrect thresholds set in Earlier or Later fields.
Solution: Review and adjust minute values to match company policy.
3. “Before departure” warnings are not triggered
Cause: Before Departure value set too high or too low.
Solution: Adjust hours to a practical timeframe (e.g., 5 hours ensures timely action).
4. Overlapping categories
Cause: Inconsistent configuration (e.g., Tiny later = 20 min, Small earlier = 20 min).
Solution: Ensure Tiny < Small < Large for both Earlier and Later.
Start with company-standard values (for example Tiny: 10–20 min, Small: 20–30 min, Large: 60–70 min).
Test after changes by simulating a flight update in a non-production environment if possible.
FAQ
Do I have to configure both Earlier and Later?
Yes. Flights can move both earlier and later.
Configure both so the system can classify changes consistently in both directions.
Should the thresholds be higher for Large than for Small and Tiny?
Yes. Keep thresholds increasing from Tiny → Small → Large.
That avoids overlaps and unexpected classification.
Last updated
Was this helpful?