Alert stays in “NOT FIRING” and notifications cannot be created

Bug Description

Please describe.
If this affects the front-end, screenshots would be of great help.

I’m trying to configure an alert on an insight so that it fires when a threshold is reached and sends a notification (email / webhook). We're sending events from an application made in Unity, using the .NET package.

The alert is created and enabled, but it never fires: it always appears in green with the status “NOT FIRING”, even when the underlying insight clearly exceeds the configured threshold.

Additionally, when I try to add a new notification to this alert, the notification panel opens but the UI does not let me select any event for the filter, and the configuration cannot be completed even if it says it is saved. Because the notification won't appear, and no email (or other notification) is ever sent.

Also, in the alerting section, the rules cannot be personalized to include the alerts with specific events and counts

How to reproduce

1. Create and save a Trend insight for a specific event, then create an Alert from that insight with a “has value” condition (for example, “more than 9”) and enable it.

2. Generate enough events so that the insight metric clearly goes above the threshold, then check the alert status in the Alerts view: it remains in “NOT FIRING” instead of firing.

3. From the same alert, click Add notification and try to configure a new notification (email / webhook): the UI does not allow selecting any event for the filter, the form is effectively incomplete, and the notification cannot be saved, so no email or webhook is ever sent.

Additional context

This behavior happens consistently every time I try to use alerts.

The main issues are:
Alert state never changes from “NOT FIRING” even when the condition is met.
Notification creation fails because no event can be selected in the filter, so the notification cannot be saved or triggered.

Debug info

- Self-Hosted Docker

No source files or tests are named in the report. Reproduce the alert condition and the Add notification flow in the self-hosted Docker setup, then trace the alert status and notification event-selection paths. Done means the alert changes to FIRING when the threshold is exceeded and a notification can be configured, saved, and delivered.