Skip to content

Alerts

The Alerts screen is a single feed of notable events across your Nexa platform — job failures, data-flow changes, jobs placed on hold, and overall system status — so you can scan what needs attention in one place. It is reached at /alerts.

Each alert is a card describing one event. The categories that surface here include:

Category Example
Job Failure A pipeline or job run failed
Change in Data Flow A schema change, such as a new attribute column on an entity
Job Hold A job was paused or held
System Status General platform health, e.g. all systems operating normally

Every alert shows a title, a description with the specifics (which job, which entity), a relative timestamp (for example, “10 Minutes Ago”), and a status.

An alert carries one of four states, shown as a colored badge:

State Meaning
New Unreviewed — needs attention
Acknowledged Seen and being handled
Failed The underlying event is a failure
Success The underlying event resolved successfully

Filter tabs across the top of the feed let you narrow to a single state:

  • All Alerts
  • Failed
  • New
  • Acknowledged
  • Success

Selecting a tab shows only alerts in that state, so you can jump straight to what is failing or still unreviewed. Each alert card also has a per-item menu for managing the entry.

Alerts consolidates review; the delivery of operational notifications comes from the parts of Nexa that own those events:

  • Automations can send an email or Slack notification at the end of a run — configure these as actions when you create an automation. This is the primary way to be notified proactively about agent and automation outcomes.
  • The Slack integration wires Nexa to your Slack workspace so notifications and agent channels can be delivered. See Slack integration.
  • Data-flow and schema changes that appear here as alerts are reviewed and committed on the Review Changes screen.
  • Job and pipeline health behind the Job Failure and Job Hold alerts is managed on the Jobs screen.