The binary log file referenced in the replica's position no longer exists on the primary (binlog was purged). Primary server was restored from backup and has a different binlog history than the replica. Binary log was corrupted on the primary. The replica's MASTER_LOG_POS is past the end of the current binlog file on the primary

Step 1: On the primary, check available binary logs: `SHOW BINARY LOGS;`. Step 2: On the replica, check current replication status: `SHOW SLAVE STATUS\G`. Step 3: If the binlog was purged, re-initialize the replica from a fresh backup of the primary.. Step 4: Reset the replica to the latest primary position: `STOP SLAVE; RESET SLAVE; CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.XXXXXX', MASTER_LOG_POS=4; START SLAVE;`

Critical severityconfiguration

Power BI Refresh Error:
1236

What does this error mean?

MySQL replication failed because the replica could not read the expected binary log position from the primary.

Common causes

1The binary log file referenced in the replica's position no longer exists on the primary (binlog was purged)
2Primary server was restored from backup and has a different binlog history than the replica
3Binary log was corrupted on the primary
4The replica's MASTER_LOG_POS is past the end of the current binlog file on the primary

How to fix it

1Step 1: On the primary, check available binary logs: `SHOW BINARY LOGS;`
2Step 2: On the replica, check current replication status: `SHOW SLAVE STATUS\G`
3Step 3: If the binlog was purged, re-initialize the replica from a fresh backup of the primary.
4Step 4: Reset the replica to the latest primary position: `STOP SLAVE; RESET SLAVE; CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.XXXXXX', MASTER_LOG_POS=4; START SLAVE;`

Frequently asked questions

How do I prevent MySQL binlog purging from breaking replication?

Set `expire_logs_days` (MySQL 5.7) or `binlog_expire_logs_seconds` (MySQL 8.0) to a value larger than the maximum expected replication lag — at least 7 days is recommended.

How do I re-initialize a MySQL replica after error 1236?

Take a consistent backup of the primary using mysqldump with --master-data=2 or use Percona XtraBackup. Restore on the replica and configure CHANGE MASTER TO using the binlog coordinates from the backup.

Can MetricSign detect when replication failure causes stale data in Power BI?

MetricSign monitors ADF pipeline failures and Power BI refresh failures — if a replica serving as an ADF source returns errors, the pipeline failure incident is surfaced immediately.

Official documentation: https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html