Enable Insights and Notifications for “No Data Returned” Scenarios

Problem Statement:

The inability to trigger Insights or notifications when a query returns no data prevents users from being alerted to potentially critical gaps, such as missing uploads, failed data integrations, or operational outages. This limitation reduces the effectiveness of the alerting system and can delay response to important data issues.

Proposed Solution: 

Enhance the Insights engine to support alerting and notifications for “no data returned” scenarios. When a query yields zero rows for a specified period or condition, the system should allow users to configure Insights that trigger notifications for these cases.

Key Requirements:

- Allow users to define Insights that specifically monitor for “no data returned” conditions.

- When a query returns zero rows, trigger the configured Insight and send notifications as per user settings.

- Clearly distinguish between “no data returned” (absence of records) and “null values in existing records” in both the UI and notification messages.

- Provide configuration options to specify the timeframes or conditions under which “no data” alerts should be evaluated (e.g., daily, weekly, per entity).

Benefits:

- Ensures users are promptly alerted to missing or incomplete data, enabling faster investigation and resolution.

- Improves data quality monitoring and operational reliability.

- Provides a more comprehensive and proactive alerting system.

Acceptance Criteria:

- Users can configure Insights to trigger when a query returns no data.

- Notifications are sent as expected when “no data” scenarios occur.

- The system clearly communicates the difference between “no data” and “null values.”

- No false positives are generated for valid zero-result scenarios (e.g., when no data is expected).

Summary:

Supporting Insights and notifications for “no data returned” scenarios will close a critical gap in data monitoring, ensuring users are aware of missing data and can take timely action.