If you’ve received an in-app or email error notification, here’s where you’ll find the resources you need to get things back on track.
Account & Billing Errors
If you’re having trouble logging into your Stitch account, this is the place to start.
Encountering errors when trying to enter your payment info into Stitch? Before you contact support, we recommend seeing if these simple fixes resolve the issue.
While typically transient, I/O errors arise from connection issues between Stitch and your data warehouse. If persistent, these errors may be indicative of a larger issue.
Stitch periodically performs checks on the connection to your destination to ensure the connection remains active and healthy. In this article are some of the most common errors you might see if Stitch has trouble performing the connection check to your destination and how to resolve them.
If you received an error notification from Stitch about writing to your data warehouse, that means we ran into an issue loading your data. There can be a variety of reasons for this, each of which is specific to the type of destination you’re using.
Received an error about Stitch loading data into your Postgres data warehouse? Check out these common errors and how to resolve them.
Received an error about Stitch loading data into your Redshift data warehouse? Check out these common errors and how to resolve them.
If you received a
VACUUM notification, it means that Stitch hasn’t been able to successfully complete
VACUUM some tables in your data warehouse for more than 10 days.
If you’ve received a ‘Dependent Views’ error for your Redshift or Panoply data warehouse, you may need to temporarily drop dependent objects.
Stitch periodically performs checks on the connection to your database to ensure the connection remains active and healthy. In this article are some of the most common errors you might see if Stitch has trouble performing the connection check to your database and how to resolve them.
Occasionally, some integrations used by Stitch may encounter bugs or other issues. Whenever we’ve identified a third-party issue - meaning on the integration provider’s end - we’ll post an update here.
When Stitch replicates data from a MySQL-backed database, it will check for the required user permissions and database server settings. If permissions or server settings aren’t properly defined, an error may arise. In this article are the errors you might see and how to resolve them.
If you see a message that asks you to re-authorize an integration, it means that Stitch’s permissions to that service have been revoked.
If Stitch is unable to connect to one of your SaaS integrations, the issue may be a security setting on the integration provider’s side.
From time to time, some of the applications and databases we integrate with may experience downtime. During these outages, Stitch may be unable to successfully connect to your data source and replicate your data.