Two transactions each hold a lock the other needs, in reverse order. ADF parallel activities updating the same rows in different orders across concurrent threads. dbt incremental models and application writes competing for the same row locks. Missing indexes causing full table scans that create broad lock contention

Step 1: Implement automatic retry for the rolled-back transaction — MySQL only rolls back one transaction, leaving the other to proceed.. Step 2: Check the last deadlock: `SHOW ENGINE INNODB STATUS;` — look for the LATEST DETECTED DEADLOCK section.. Step 3: Ensure transactions always acquire locks in the same order across all application paths.. Step 4: Add indexes to reduce the number of rows locked during UPDATE/DELETE operations.

High severityresource

Power BI Refresh Error:
1213

What does this error mean?

MySQL detected a deadlock between two or more transactions and rolled back one of them to resolve the cycle.

Common causes

1Two transactions each hold a lock the other needs, in reverse order
2ADF parallel activities updating the same rows in different orders across concurrent threads
3dbt incremental models and application writes competing for the same row locks
4Missing indexes causing full table scans that create broad lock contention

How to fix it

1Step 1: Implement automatic retry for the rolled-back transaction — MySQL only rolls back one transaction, leaving the other to proceed.
2Step 2: Check the last deadlock: `SHOW ENGINE INNODB STATUS;` — look for the LATEST DETECTED DEADLOCK section.
3Step 3: Ensure transactions always acquire locks in the same order across all application paths.
4Step 4: Add indexes to reduce the number of rows locked during UPDATE/DELETE operations.

Frequently asked questions

Which transaction does MySQL roll back in a deadlock?

MySQL rolls back the transaction with the least 'weight' — typically the one that has done the least work (modified fewest rows). The other transaction continues successfully.

How does ADF handle MySQL deadlocks?

ADF does not automatically retry on deadlock errors. Configure retry policy on the pipeline activity (up to 3 retries with a 30-second delay) to handle transient deadlocks gracefully.

Can MetricSign detect recurring deadlock patterns?

Yes — MetricSign tracks ADF pipeline failure frequency. Recurring failures with the same MySQL error code indicate a systemic deadlock pattern that needs investigation.

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