What causes FAILOVER_IN_PROGRESS?

An operator issued ALTER FAILOVER GROUP ... PRIMARY while a scheduled or manually triggered replication refresh was still in progress. A previous failover attempt partially completed and left the group in a transitional state that blocks a new failover. An automated orchestration tool retried a failover command too quickly before the preceding refresh completed

How do I fix FAILOVER_IN_PROGRESS?

Step 1: Query REPLICATION_GROUP_REFRESH_PROGRESS_BY_JOB on the secondary account to check whether a refresh is still running.. Step 2: Wait for the refresh to complete, or cancel it with ALTER REPLICATION GROUP SUSPEND IMMEDIATE on the secondary account.. Step 3: After the refresh or its cancellation completes, re-issue the failover command: ALTER FAILOVER GROUP PRIMARY.. Step 4: For automated failover orchestration, add a pre-check that verifies no refresh is in progress before issuing the failover command.

High severityexecution

Power BI Refresh Error:
FAILOVER_IN_PROGRESS

What does this error mean?

A Snowflake failover or secondary promotion request was rejected because a replication refresh is currently running for the target failover group, and both operations cannot proceed simultaneously.

Common causes

1An operator issued ALTER FAILOVER GROUP ... PRIMARY while a scheduled or manually triggered replication refresh was still in progress
2A previous failover attempt partially completed and left the group in a transitional state that blocks a new failover
3An automated orchestration tool retried a failover command too quickly before the preceding refresh completed

How to fix it

1Step 1: Query REPLICATION_GROUP_REFRESH_PROGRESS_BY_JOB on the secondary account to check whether a refresh is still running.
2Step 2: Wait for the refresh to complete, or cancel it with ALTER REPLICATION GROUP <name> SUSPEND IMMEDIATE on the secondary account.
3Step 3: After the refresh or its cancellation completes, re-issue the failover command: ALTER FAILOVER GROUP <name> PRIMARY.
4Step 4: For automated failover orchestration, add a pre-check that verifies no refresh is in progress before issuing the failover command.

Frequently asked questions

Can I force a failover even while a refresh is running?

You can cancel the in-progress refresh with ALTER REPLICATION GROUP ... SUSPEND IMMEDIATE and then proceed with the failover, accepting that the secondary may not have the very latest data.

Does canceling a refresh lose data on the secondary?

No. Canceling a refresh leaves the secondary at its last successfully committed state. No data is lost from previously completed refreshes.