Skip to main content

Notifications

The Notifications page provides a centralized view of events and alerts across your Onehouse project. Notifications are delivered through multiple channels and organized by severity to help you monitor your data infrastructure.

Notification Channels​

  • In-app Notifications: Enabled by default. Cannot be turned off.
  • Email Notifications: Enabled by default. Cannot be turned off.
  • Slack Notifications: Follow the instructions in the docs to set up the Slack integration and receive notifications in Slack.

Email Recipients​

Email notifications are sent to:

  • Project and account admins — project-level notifications (such as flow failures and resource lifecycle events) are sent to the project's admins; account-level notifications (such as API key expiry) are sent to the account's admins.
  • The configured Notifications Email — if a Notifications Email is set for the project, that address always receives the project's notification emails, in addition to the admins above. This is useful for routing alerts to a shared distribution list or on-call alias so the whole team can see them, not just admins.

To configure the address, go to Project Settings → Communication Preferences → Notifications Email. It defaults to the project creator's email and can be changed to any valid email address (for example, a team alias like team-alias@company.com).

Severity Categories​

Notifications are organized into four severity tabs:

Errors​

Critical issues that require immediate attention.

  • Flow failed after retries
  • Metadata extractor errors
  • API key expired

Warnings​

Conditions that may lead to issues if not addressed.

  • Flow delayed (and subsequent recovery notifications)
  • Max OCU limit reached
  • API key expiring soon
  • Missing records in table

Information​

Informational updates about resource lifecycle events.

  • Resources created or deleted (Flows, Sources, Databases, Data Lakes, Catalogs, Tables, Users)
  • Flows paused or resumed
  • Savepoints created
  • API key approaching expiration
  • First table processed

Recommendations​

Suggestions for optimizing your data infrastructure.

  • Data skew detected in partitions
  • Log file count increased per partition
  • Status of table processing updates

Notification Actions​

  • Dismiss: Archive notifications you have reviewed. Dismissed notifications can be reactivated.
  • Activate: Restore previously dismissed notifications.
  • Bulk actions: Select multiple notifications to dismiss or activate in batch.

Filtering​

Filter notifications by:

  • Type — narrow to specific notification categories.
  • Lakes — filter by data lake.
  • Databases — filter by database.
  • Tables — filter by table.
  • Sources — filter by data source.
  • Creation Date — filter by time range.

Notification Settings​

For community edition projects, click the settings icon on the Notifications page to configure thresholds for:

  • Data Skew Per Partition — enable or disable alerts and set a custom threshold.
  • Number of Log Files Per Partition — enable or disable alerts and set a custom threshold.

Troubleshooting​

Some admins are not receiving Flow-failure alerts​

Email and in-app notifications are delivered to all Project Admins by default. If a specific admin is missing alerts:

  1. Verify the role. The user must hold the Project Admin role, not just Project Member. See Permissions.
  2. Refresh the console. Admins added shortly after a project's permissions or accounts system was updated may need to refresh the Onehouse console to pick up notification routing.
  3. Check Slack integration health if Slack is the affected channel — re-authorize the Slack integration if messages have stopped arriving.

If alerts are still missing after these checks, contact support with the project ID, the affected admin's email, and the time window of the missed notification.