Having trouble with your destination? Whether it’s an issue with setup or connections, these are some of the most common causes of destination problems.
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.
Amazon Redshift / Panoply
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.
If you’re having trouble with setting up or connecting to your Panoply data warehouse in Stitch, try these troubleshooting steps before reaching out to support.
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.
Received an error about Stitch loading data into your Postgres data warehouse? Check out these common errors and how to resolve them.