Enable data delivery alerts for RudderStack sources and destinations.

RudderStack’s notifications feature lets you enable data delivery alerts for sources, cloud destinations, and warehouse destinations. You can subscribe or unsubscribe to alerts for a particular resource once your admin enables the alerts for that resource.

Enabling notifications

To enable the alerting service for a particular source or destination you must have admin permissions.

  1. Navigate to the source or destination in the RudderStack dashboard.
  2. Click the Settings tab.
  3. Toggle the Enable Notifications setting to allow members to subscribe to notifications for that resource.
Enable notifications
The Enable Notifications option is only available to users with admin permissions.

Managing alerts

To manage the individual alerts per connection, navigate to the Settings menu in the main left-hand navigation and click the Notifications tab.

Notification settings

In the notifications area, you can manage your alert subscriptions for errors related to sources, cloud destinations, and warehouse destinations. As mentioned above, the notifications must have been enabled by an admin.

From the Notifications tab, click the Manage Subscription button to toggle on/off subscriptions to all of the sources, destinations, and warehouse destinations your admin has enabled.

Manage subscriptions

From this view you can toggle your own notifications on or off. Clicking the arrow will take you to the Settings page for that connection.

Alert types

RudderStack will send email alerts for two types of errors: datatype mismatch and delivery errors. In addition, it also sends some delivery warning alerts.

Refer to the following tables for the error descriptions/warnings and the necessary actions to resolve them.

Datatype mismatch errors

Error descriptionCustomer actions
Message Type is not present. Aborting message.event.type is missing from the payload. Make sure you include the message type.
Event name is required.event.event is missing from the payload. Include a valid event name.
Unable to process without anonymousId or userId.Make sure to include all required fields in the payload for successful event delivery.
Missing required value from <source key>.Make sure to include all of the required fields from the list for a successful event delivery.
Event is required for track call.event.event is missing from the payload. Make sure to include a valid event name.

Delivery errors

Error descriptionCustomer actions
Message format type not supported.The destination does not support this message type. Ensure that you pass only the supported event type.
Invalid payload for the destination.The inputted JSON payload does not match the expected request body.
Event is not configured in your RudderStack dashboardMake sure to either filter out the event through a user transformation or add a new event in the RudderStack dashboard.
Invalid API Key. Aborting message.Ensure that a valid API key has been added to the RudderStack dashboard.
Invalid Account Id. Aborting message.Ensure that a valid Account ID key has been added to the RudderStack dashboard.
userId or email is mandatory for this request.Make sure to include userId/email in the payload for successful event delivery.
Event timestamp should be within last <timeline>.The event needs to be within the last <timeline> for successful delivery of the event. Any event older than <timeline> would result in failures.

Delivery warnings

WarningCustomer actions
You’re reaching the column limit in your <table_name> table.Use any of the following approaches:
  • Go to your warehouse and delete (drop) the unwanted table columns.
  • If you’re syncing semi-structured event data that is not defined by a fixed schema, you can leverage RudderStack’s JSON Column Support feature to send your data.

For more information, refer to the Warehouse FAQ guide.
Warehouse column names are not matching the destination views as the views are outdated. Recreate your views so that they point to the latest column names and then drop the older columns. Please use the queries in the documentation to drop the columns.Your deprecated columns will be of the format <column-name>-deprecated-<uuid>.

Follow these steps:
  1. Find the <table> and the <column> by querying your metadata tables. Ignore the columns that have the deprecated column format already. For example, in case of Redshift, your query will something like:

    select table_name, column_name from INFORMATION_SCHEMA.COLUMNS where table_schema = '<schema>' and column_name like '%-deprecated-%';

  2. Once you find the <table> and the <column>, drop the columns. A sample Redshift query is shown below:

    ALTER TABLE <table> DROP COLUMN "<column>" CASCADE;

  3. Finally, recreate your views. A sample Redshift query is shown below:

    CREATE VIEW <table-view> AS SELECT * FROM <table>;

Questions? Contact us by email or on Slack