Propel docs home page
Search...
⌘K
Sign up
Console
Console
Search...
Navigation
Guides
Recovering from a failed sync
Serverless Cloud
Ingestion
Query APIs
Embeddable UI
Changelog
Ingestion
Get Started
Overview
Streaming
Kafka
Webhooks
Amazon Data Firehose
Twilio Segment
Data warehouses
Snowflake
Overview
Setup guide
Guides
Change tracking
Snowflake + dbt
Failed syncs
Amazon S3
Databases
Amazon DynamoDB
ETL Platforms
Fivetran
Airbyte
On this page
Recovering from a failed sync due to broken or stale streams
For ReplacingMergeTree tables:
For MergeTree tables:
Guides
Recovering from a failed sync
What to do when a Snowflake sync fails.
Recovering from a failed sync due to broken or stale streams
When a sync fails because of a broken or stale stream, follow these steps based on your table engine:
For ReplacingMergeTree tables:
In the Propel console, click the
“Re-sync”
button.
This action will:
Recreate the stream
Re-ingest the data
Deduplicate the data
For MergeTree tables:
Ensure
change tracking is enabled
on the Snowflake table.
Create a new Data Pool with identical configuration settings.
Allow the initial sync to complete.
Transfer metrics from the old Data Pool to the new one.
Remove the old Data Pool.
By following these steps, you’ll ensure your data remains synchronized and accessible in Propel.
Was this page helpful?
Yes
No
Snowflake + dbt
Overview
Assistant
Responses are generated using AI and may contain mistakes.