Skip to main content
Alerts notify you by email when something happens in your account: an API goes down, a database stops responding in time, a pre-aggregation build fails, or a build finishes.

Manage alerts

Click Alerts in the sidebar to see every alert configured on the account. Click New alert to add one, or use the edit and delete icons on a row to change or remove an existing alert. On plans below Enterprise, only account administrators can manage alerts. On the Enterprise plan, access also follows the AlertsCreate, AlertsRead, AlertsUpdate, and AlertsDelete actions. Administrators always have access, and the built-in Developer and AIBI Developer roles carry all four. The same four actions also govern budgets.
These four actions are not among the ones you can pick when you build a custom role. To grant them, assign a built-in Developer or AIBI Developer role.

Event types

Each alert watches a single event type: The first three are conditions: Cube emails you when the condition starts, then emails you again with a Resolved — subject prefix when it clears. While a condition persists, Cube does not re-send the same alert for a while — 1 hour for API outages and database response timeouts, 3 hours for pre-aggregation build failures.
Build completed fires when a build finishes, whether it succeeded or failed. The subject line reads Build finished with status: <status>. It is a point-in-time event, so it has no resolved email.

Deployments

An alert applies either to All deployments in the account, or to a Specific set you pick. Choosing Specific requires at least one deployment.

Recipients

Under Send alerts to, pick either All users on this account or Specific users. Under Also send to, add any number of custom email addresses; these are additive, and a custom address on its own is a valid set of recipients.
All users on this account only reaches users who have signed in at least once. Users who were invited but never signed in do not receive alerts.

Delivery

Alerts are delivered by email only — there is no Slack, webhook, or PagerDuty delivery. Scheduled refresh notifications, which cover dashboard refresh outcomes, are a separate feature with its own delivery channels. To alert from your own observability stack instead, export telemetry with monitoring integrations.