What causes REPLICATION_CONFLICT?

An object in the source account has the same name as an existing object in the target account, causing a conflict on refresh. The primary database contains external tables, which are not supported for cross-cloud replication. A schema change (column add/drop) in the primary was not compatible with an existing view in the secondary. Network connectivity between the source cloud region and the target cloud region was disrupted during refresh

How do I fix REPLICATION_CONFLICT?

Step 1: Check the replication group refresh status: SELECT * FROM TABLE(INFORMATION_SCHEMA.REPLICATION_GROUP_REFRESH_HISTORY()) ORDER BY PHASE_TIME DESC;. Step 2: Identify the conflicting object from the error details and resolve the naming conflict or drop the incompatible object.. Step 3: For external table conflicts, exclude the external table from the replication group.. Step 4: Re-run the refresh: ALTER REPLICATION GROUP REFRESH;. Step 5: After a successful refresh, schedule regular replication health checks to catch conflicts early.

High severitydata_quality

Power BI Refresh Error:
REPLICATION_CONFLICT

What does this error mean?

A Snowflake cross-cloud replication refresh failed because a naming conflict, unsupported object type, or schema mismatch was detected between the primary and secondary account.

Common causes

1An object in the source account has the same name as an existing object in the target account, causing a conflict on refresh
2The primary database contains external tables, which are not supported for cross-cloud replication
3A schema change (column add/drop) in the primary was not compatible with an existing view in the secondary
4Network connectivity between the source cloud region and the target cloud region was disrupted during refresh

How to fix it

1Step 1: Check the replication group refresh status: SELECT * FROM TABLE(INFORMATION_SCHEMA.REPLICATION_GROUP_REFRESH_HISTORY()) ORDER BY PHASE_TIME DESC;
2Step 2: Identify the conflicting object from the error details and resolve the naming conflict or drop the incompatible object.
3Step 3: For external table conflicts, exclude the external table from the replication group.
4Step 4: Re-run the refresh: ALTER REPLICATION GROUP <name> REFRESH;
5Step 5: After a successful refresh, schedule regular replication health checks to catch conflicts early.

Frequently asked questions

Does cross-cloud replication support all Snowflake object types?

Most objects are supported, but external tables, external stages in some configurations, and Snowflake Marketplace shares have restrictions. Check the Snowflake replication considerations documentation for the current object compatibility matrix.

Can I replicate data in real time with Snowflake cross-cloud replication?

No — cross-cloud replication is near-real-time with a configurable refresh schedule. For lower RPO, set the replication group refresh interval to 1 minute (the minimum).