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 alerts for it.
You must have admin permissions to enable notifications for a particular source or destination.
Navigate to the source or destination in the RudderStack dashboard.
Click the Settings tab.
Toggle the Enable Notifications setting to allow members to subscribe to notifications for that resource.
The Enable Notifications option is only available to users with admin permissions.
To manage the individual alerts per connection, go to Settings > Your Profile and click the Notifications tab.
In this tab, you can manage alert subscriptions for errors related to sources, cloud destinations, and warehouse destinations. As mentioned above, the notifications must have been enabled by an admin.
Click the Manage Subscriptions button to toggle on/off subscriptions to specific sources, cloud destinations, and warehouse destinations. You will receive email alerts only for the subscribed resources.
Click the arrow to go the Settings tab of the particular resource.
RudderStack will send email alerts for two types of errors: datatype mismatch and delivery errors. In addition, it also sends some delivery warning alerts.
See the following tables for the error descriptions/warnings and the necessary actions to resolve them.
Datatype mismatch errors
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.
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 dashboard
Make 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.
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.
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:
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-%';
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;
Finally, recreate your views. A sample Redshift query is shown below:
CREATE VIEW <table-view> AS SELECT * FROM <table>;
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
for the working of basic functionalities of the website. We also use third-party cookies that
analyze and understand how you use this website. These cookies will be stored in your browser
consent. You also have the option to opt-out of these cookies. But opting out of some of these
have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.