AeroAPI Alerts Not Being Delivered – Confirmed Flight Event Without Notification (Alert ID 106060439)

[BKFALCAO]

Hello FlightAware Support Team,

I hope you are doing well.

We are reaching out to request your assistance in investigating an issue with AeroAPI alerts not being delivered to our webhook endpoint, despite correct configuration and successful validation.

---

Specific Example (Confirmed Case)

We would like to highlight the following alert, which is now associated with a flight that has already departed:

• Alert ID: 106060439

• Flight: TAP Air Portugal 298 (TAP298 / TP298)

• Start Date: 2026-03-25

• End Date: 2026-03-29

• Enabled: true

Alert configuration:

{
  "ident": "TAP298",
  "start": "2026-03-25",
  "end": "2026-03-29",
  "target_url": "https://falcao.mimo.ao/webhook/flights/notifications",
  "enabled": true,
  "events": {
    "arrival": true,
    "departure": true,
    "cancelled": true,
    "diverted": true,
    "filed": true,
    "out": true,
    "off": true,
    "on": true,
    "in": true
  }
}

---

Flight Status (Verified)

We have confirmed that the flight is currently in progress:

• fa_flight_id: TAP298-1774246370-airline-1005p

• Origin: FNBJ (Luanda)

• Destination: LPPT (Lisbon)

• Actual Out: 2026-03-25T08:43:00Z

• Actual Off (Takeoff): 2026-03-25T08:59:00Z

• Status: In Flight / On Time

• Progress: 33%

This confirms that multiple alert-triggering events (e.g., out, off, departure) have already occurred.

---

Issue Description

Despite the correct configuration and confirmed flight activity:

• We are not receiving any webhook notifications

• The Notifications section in the FlightAware portal is empty

• No delivery attempts or failures are visible

• The alert is active and within a valid time window

• All relevant events are enabled, including filed

---

Our Current Setup

• Webhook endpoint (HTTPS, publicly accessible):

  https://falcao.mimo.ao/webhook/flights/notifications
  
  

• Endpoint is also configured globally in our account:

{
  "url": "https://falcao.mimo.ao/webhook/flights/notifications"
}

• The endpoint:

  • Accepts POST requests

  • Returns HTTP 200 OK

  • Has been successfully tested manually

• Alerts are:

  • Created in advance (1–2 days before flight)

  • Configured with explicit target_url

  • Enabled and active

  • Include all relevant events

---

Conclusion

This is a confirmed case where:

• A valid alert exists

• The flight has already departed and is in progress

• Multiple triggering events have occurred

• No notifications were generated or delivered

This suggests a potential issue with alert triggering or delivery on the AeroAPI side.

---

What We Need Help With

We would appreciate your assistance in verifying:

1. Whether alert ID 106060439 is being triggered internally

2. If any delivery attempts were made to our webhook endpoint

3. Whether there are any matching or filtering constraints affecting this alert

4. If alerts based solely on ident are sufficient for reliable triggering

5. Whether additional parameters (origin/destination) are required

---

We are happy to provide any additional information needed.

Thank you very much for your support.

Best regards,
Luis

[Fischer6385]

Hello,

I can confirm there were 4 triggers sent for the alert with ID 106060439 (out, off, on, in). There aren’t any issues with the alert filters or the ident, and no additional parameters would be required here. The only suspect that could be causing the issue is your endpoint itself.

[BKFALCAO]

Hello,

Thank you for your confirmation.

It is very helpful to know that 4 triggers were sent for alert ID 106060439 (out, off, on, in), and that there are no issues with the alert filters or the ident.

Since we have already tested our webhook manually and it responded correctly, we would like to investigate further what may be happening during the actual AeroAPI delivery attempts.

Could you please help us with the following:

• Any available delivery logs or traces for those webhook attempts

• The timestamps of the delivery attempts

• The HTTP response codes received from our endpoint

• Any timeout, TLS, connection, or delivery error details you may have on your side

This would help us determine whether the requests are reaching our server and whether the issue is occurring at transport level or within our endpoint handling.

In addition, we would like to suggest creating and monitoring a new test alert so we can follow it closely from both sides and identify exactly where the failure is occurring. We believe this would help us verify the end-to-end delivery path under real conditions.

If there is any recommended way from your side to replay or simulate webhook deliveries, that would also be very helpful for us.

Thank you again for your support.