# About Notifications from Treasure AI Treasure AI notifies you through four independent channels: the Status Page, automated emails from jobs and workflows, overage and usage emails configured in Treasure Console, and individual emails from Treasure AI Technical Support. Each channel has its own trigger, its own recipient list, and its own place to subscribe or configure — so a team subscribed to only one channel can miss the notification that matters most. This page maps all four, so you know what arrives, who receives it, and where to change it. ## What Notifications Treasure AI Sends | **Channel** | **What it announces** | **Who receives it** | **Where to subscribe or configure** | | --- | --- | --- | --- | | Status Page | Scheduled maintenance and large-scale incidents affecting Treasure AI services | Anyone who subscribes — no account required | [Service Status Dashboard](/support/service-status-dashboard) | | System notifications | Failures and recoveries of your own scheduled queries, scheduled data imports, workflows, and Audience Studio activations | The job, workflow, or activation owner — varies by type, see below | Audience Studio activations allow optional recipient configuration; everything else is automatic and not configurable | | Overage and usage notifications | Usage that exceeds or approaches a contracted limit, plus optional weekly and monthly usage reports | The Recipient Emails list, or the account owner if that list is empty | [Overage Notification Settings](/products/control-panel/settings/configuring-overage-notification-settings) | | Individual notifications from Technical Support | Account-specific matters that the automated channels don't cover | The Recipient Emails list from Overage Notification Settings | Not configurable separately — maintain the same Recipient Emails list | ## Status Page Announcements The Treasure AI Status Page at [https://status.treasure.ai/](https://status.treasure.ai/) publishes scheduled maintenance windows and large-scale incidents. It is the only Treasure AI notification channel that anyone can subscribe to without a Treasure AI account, and it is the channel to watch when you need to know whether a problem is yours or ours. Status Page announcements are platform-wide. They never describe what happened to an individual job, workflow, or account — that is what system notifications cover. You subscribe per region and per component (Web Interface, REST API, Workflow, CDP API, and others), and you can receive updates by email, SMS, or RSS. Treasure AI recommends that every paid account has at least one subscriber. For the subscription steps and the full component list, see [Service Status Dashboard](/support/service-status-dashboard). ## System Notifications for Jobs and Workflows System notifications are automated emails that Treasure AI sends about your own resources when a job, workflow, or activation fails — and, for some types, when it recovers. The important difference between types is *how often* they arrive: scheduled queries and scheduled data imports notify you once per failure streak, while workflows and Audience Studio activations notify you on every occurrence. | **Resource type** | **On failure** | **On recovery** | **Default recipient** | | --- | --- | --- | --- | | Scheduled query (Trino or Hive) | Notified on the first failure only. A run that keeps failing does not send a new email each time. | Notified once, when a run succeeds again after one or more failures. | The owner of the scheduled query | | Scheduled data import (Integration Hub source) | Notified on the first failure only, the same as scheduled queries. | Notified once, when the import succeeds again. | The owner of the data source | | Workflow | Notified on every failure. A workflow that fails daily sends an email daily. | No recovery notification. | The user who last updated the workflow project | | Audience Studio activation | Notified on every failure, if failure notifications are enabled on the activation's schedule. Failures also notify the parent segment creator. | No recovery notification. Success notifications are available as a separate opt-in. | The recipients configured on the activation, up to 20 | ### Scheduled Queries and Scheduled Data Imports Scheduled queries and scheduled data imports share one notification model: Treasure AI emails the resource owner the first time a run fails, stays quiet while the failure repeats, and emails again once a run succeeds. That design keeps a broken nightly job from filling your inbox, but it also means a single email can represent weeks of failures — check the job history, not your inbox, to judge how long something has been broken. A scheduled resource that keeps failing because of a configuration error may be disabled on the Treasure AI side. For the exact message text of both the failure and the recovery email, see [Automatic Error Notification for Scheduled Jobs](/products/customer-data-platform/data-workbench/queries/scheduled/automatic-error-notification-for-scheduled-jobs). ### Workflows Treasure Workflow notifies you on every occurrence, not once per streak, and it covers more than task failures: a scheduled workflow that cannot start, a task timeout, a workflow timeout, an attempt failure, an SLA violation, and a trigger run failure each send their own email. Workflow notifications are sent from `Treasure AI ` — allowlist that address if your organization filters incoming mail. The recipient is the user who last updated the workflow project, not the person who ran it. For manual executions, notifications go to the workflow project owner. For the trigger conditions and email subject lines, see [About Workflow Email Notifications](/products/customer-data-platform/data-workbench/workflows/about-workflow-email-notifications). To send workflow notifications somewhere else — a shared mailbox, a different team, or a success notification — define them in the workflow itself with the `mail>` operator or the `sla:` directive. See [Creating Workflow Notifications](/products/customer-data-platform/data-workbench/workflows/creating-workflow-notifications). ### Audience Studio Activations Audience Studio activations are the one system notification type where you choose the recipients up front. On each activation's schedule you can select up to 20 recipients and enable success notifications, failure notifications, or both. When an activation fails, Treasure AI also emails the parent segment creator, in addition to the recipients you configured. Two consequences are worth planning for: notification settings are copied when you copy an activation, and removing a user from your account does not remove them from an activation's recipient list. Update the list yourself, or notifications keep going to a person who has left. For the schedule fields and the notification options, see [Schedule an Activation](/products/customer-data-platform/audience-studio/activation/schedule-an-activation). ## Overage and Usage Notifications Overage notifications tell an account administrator that a metric's usage — storage capacity or compute hours, for example — has exceeded or is approaching its contracted limit. Unlike system notifications, they concern the account rather than an individual job, and an administrator controls them from Treasure Console. Overage Notification Settings control the notification language, whether overage and approaching-limit emails are sent, whether the account also receives a weekly or monthly usage report, and the Recipient Emails list of up to 20 addresses. If Recipient Emails is empty, Treasure AI sends these notifications to the account owner instead. The per-metric thresholds themselves are not configurable in Treasure Console. Contact your Customer Success representative to change a threshold. For the settings table and the steps to edit them, see [Overage Notification Settings](/products/control-panel/settings/configuring-overage-notification-settings). ## Individual Notifications from Treasure AI Technical Support When something needs your attention that no automated channel covers, Treasure AI Technical Support contacts you directly. These notifications are written by a person, sent case by case, and go to the Recipient Emails list in [Overage Notification Settings](/products/control-panel/settings/configuring-overage-notification-settings) — the same list as overage notifications. Typical reasons include a defect that affects your account specifically, and a request to change how a workload is run when usage patterns are excessive or unsupported. Because this channel reuses the overage Recipient Emails list, that list is the single place that determines whether account-level notifications reach the right people. Keep it current even if your account never hits an overage. ## Frequently Asked Questions ### Which Notification Channel Should Every Account Subscribe To? At minimum, two. Subscribe at least one person to the [Status Page](/support/service-status-dashboard) so platform-wide incidents reach your team, and keep the Recipient Emails list in [Overage Notification Settings](/products/control-panel/settings/configuring-overage-notification-settings) populated so overage notifications and Technical Support notices reach an active mailbox. System notifications need no subscription — they follow resource ownership automatically. ### Why Did a Job Fail for a Week Without Sending an Email Every Day? That is the intended behavior for scheduled queries and scheduled data imports. Treasure AI notifies the owner on the first failure, stays quiet while the same failure repeats, and notifies again when a run succeeds. Workflows behave the opposite way: they notify on every failure. ### Can I Change Who Receives a Workflow Failure Notification? Not in the default notification — it goes to the user who last updated the workflow project, or to the project owner for a manual execution. To notify someone else, add a custom notification to the workflow with the `mail>` operator. See [Creating Workflow Notifications](/products/customer-data-platform/data-workbench/workflows/creating-workflow-notifications). ### Will Removing a User From the Account Stop Their Notifications? Not everywhere. System notifications follow resource ownership and stop when ownership changes, but manually maintained lists do not clean themselves up: an Audience Studio activation's recipient list and the overage Recipient Emails list keep the address until someone edits it. ## Next Steps - [Service Status Dashboard](/support/service-status-dashboard) — subscribe to maintenance and incident announcements. - [Overage Notification Settings](/products/control-panel/settings/configuring-overage-notification-settings) — set the recipients for account-level notifications. - [Contacting Treasure Support](/support/contacting-treasure-data-support) — reach Technical Support when a notification needs follow-up.