Already have an account? Sign in

Notifications Overview and Reference

To ensure you’re kept in the loop when Stitch encounters issues, Stitch will trigger in-app and email notifications.

In this guide, we’ll cover:

• Notification urgency levels

• Stitch’s notification categories

• How in-app notifications work

• How email notifications work

• A reference of Stitch’s email notifications

Notification levels

Stitch notifications are assigned levels of urgency as follows:

• Warning - Data has been replicated, but something may require your attention.For example: Your account nearing its row usage limit.

• Critical - Data can’t be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration’s schedule, but replication will not be successful until the issue is resolved.For example: Integration or destination authentication errors.

• Delay - Data is temporarily not replicating. Replication will resume when the issue is resolved.For example: Insufficient integration API quota.

Refer to theNotification reference section for more info about the issues that trigger notifications and the level assigned to each issue.

Notification categories

Stitch notifications are grouped into the following categories:

• Account - Notifications that are sent when your Stitch account requires your attention. These notifications are relevant to the account itself, the account’s payment method, etc.

• Integration - Notifications that are sent when Stitch encounters issues connecting to an integration.

• Destination - Notifications that are sent when Stitch encounters an issue with your destination.

• Replication - Notifications that are sent when Stitch encounters issues during the replication process.

• Internal - Notifications that are sent when Stitch is experiencing internal issues. While these issues are typically transient, we recommend checking theStitch status page for reported outages if you receive these notifications.

For more info about the notifications in each category, refer to theNotification reference section.

In-app notifications

When Stitch encounters an issue or something requires your attention, a notification will display in theNotifications tab of your account:

In-app notification recipients

In-app notifications are visible to all team members in a Stitch account.

In-app notification visibility

All notifications listed in theNotification reference will display in theNotifications tab shortly after they’re triggered.

Note: Email notifications for some issues may not be sent immediately after the issue occurs. Refer to theEmail notification delays section for more info.

In-app notification resolution

Notifications in theNotifications tab will continue to display until the issue that triggered the notification is resolved or dismissed.

Email notifications

For any issue listed in theNotification reference, Stitch will send an email version of the notification to all team members in a Stitch account.

Email notification recipients

Email notifications are sent to all team members in a Stitch account.

If your account also has thecustom email notification list feature enabled, email notifications will also be sent to the email addresses in this list that have anEnabled status.

Note: The only exceptions are:

• The monthly billing invoice, which is sent only to the team member who originally entered the account’s payment method details.
• If the user opts out of replication error notifications.Users who opt out of replication error notifications will still receive general email notifications. Refer to thenotification reference for each individual notification’s opt out status.

Email notification from address

All email notifications from Stitch are sent fromhttps://community.qlik.com/t5/Support/ct-p/qlikSupport.

Email notification subject lines

Notifications from Stitch will have a subject line similar to the following:Stitch Notification - <description of issue>

Email notification delays

Some email notifications may not be sent immediately after the issue occurs. Stitch implements an email send delay for some notification types to provide transient issues the opportunity to resolve themselves. Ideally, this means your inbox orexternal notification service won’t be spammed with notifications for non-actionable items.

The delay Stitch uses depends on the notification/issue type. Refer to theNotification reference section for the delay used by each notification type.

Notification reference

In this section is info about the email notifications Stitch will send to the users of your account. This includes a description of the issue triggering the notification, the email’s subject, urgency level, send delay (if any), potential causes, and the content of the email notification.

• Warning level notifications

• Critical level notifications

• Delay level notifications

Warning level notifications

When warning level notifications are sent, it means that data has been replicated, but something may require your attention.

• Approaching row limit

• Row limit reached

• Amazon Redshift VACUUM

• Missing or deleted database Replication Key

• Unable to deliver post-load hook

Approaching row limit

Sent when the usage for the current billing period surpasses 70 or 90% of the account’s row limit.

Row limit reached

Sent when the usage for the current billing period reaches 100% of the account’s row limit.

Amazon Redshift VACUUM

Applicable only to Amazon Redshift destinations. Sent when Stitch hasn’t successfully performed aVACUUM operation on tables in your Amazon Redshift destination.

Missing or deleted database Replication Key

Applicable only to non-Singer database integrations. Sent when Stitch is unable to detect the Replication Key for a selected database integration table.

Unable to deliver post-load hook

Sent when Stitch is unable to deliver a webhook notification to apost-load webhook URL.

Back to Warning notification reference

Critical level notifications

When critical level notifications are sent, it means that data can’t be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration’s schedule, but replication will not be successful until the issue is resolved.

• Free trial expiration

• Account inactivity

• SaaS integration authentication error

• Database integration error

• Data warehouse error

• Error persisting table data

• Extraction exit status

• Data loading error

• Unable to load data

• SSH tunnel connection error

Free trial expiration

Sent when the account’s free trial period has ended and a plan has not been selected. Stitch will automatically pause your integrations when the trial expires, and they will remain paused until a plan is selected or the account is deactivated.

Account inactivity

Sent when data has not been loaded into the account’s destination for more than 40 days.

SaaS integration authentication error

Applicable only to non-Singer SaaS integrations. Sent when Stitch encounters issues connecting to or replicating data from a SaaS integration.

Database integration error

Applicable only to non-Singer database integrations. Sent when Stitch encounters issues connecting to or extracting data from a database integration.

Data warehouse error

Sent when Stitch can’t load data into the account’s destination due to insufficient database user privileges.

Error persisting table data

Applicable only to non-Singer database integrations. Sent when Stitch is unable to persist extracted data for a table to your destination.

Extraction exit status

Applicable only to Singer-backed integrations. Sent when Stitch encounters critical issues during the Extraction phase of the replication process.

Data loading error

Sent when Stitch encounters issues loading data to the account’s destination.

Unable to load data

Sent when Stitch cannot load data into the account’s destination because the destination doesn’t support it.

SSH tunnel connection error

Applicable only when an SSH tunnel is being used to connect to the destination. Sent when Stitch cannot load data into the account’s destination because Stitch encountered an error creating an SSH tunnel.

Back to Critical notification reference

Delay level notifications

When delay level notifications are sent, it means that data is temporarily not replicating. Replication will resume when the issue is resolved.

• SaaS integration API rate limit

• Internal loading

SaaS integration API rate limit

Applicable only to non-Singer SaaS integrations. Sent when an integration has insufficient API quota. This applies to integrations that use APIs that enforce API quotas - for example, Google Analytics. Replication will continue when additional quota becomes available.

Internal loading

Sent when an internal Stitch issue has prevented successful data loads to your destination. Stitch will automatically retry loading until the issue is resolved.

Back to Delay notification reference

Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.