Hi,
The InsertDeleteConflict / "This won’t work because it would move cells in a table on your worksheet" error is raised by the Microsoft Graph Excel API, not by Power Automate itself. It means: when Graph tried to extend the table by one row, something on the sheet to the right of or below the table blocked the insertion. The row often still appears because Graph retries the write through a different path, but the action is still reported as failed — which is what eventually triggered the auto-disable.
Why this happens even when the area below the table looks empty
- Excel evaluates "blocking" cells based on the used range, not what’s visible. A stray space, a cleared-but-not-deleted format, or a name/comment anywhere to the right of the last table column counts as occupied.
- If a second table, named range, chart, image, or data-validation region sits on the same rows the table would expand into, Graph refuses to push it.
- If the file is opened by another session (a co-author, an Excel desktop instance, or a previous run that left the file locked) the table can be in a state where inserts are rejected.
- Files stored in SharePoint with "Always keep on this device / Files On-Demand" sometimes return InsertDeleteConflict when the cached copy is out of sync with the cloud copy.
What to try, in order
- Reset the used range. Open the workbook in Excel desktop → press Ctrl + End. If the cursor lands far below or to the right of your table, that’s the cause. Select the rows/columns between your table’s last cell and that ghost end-of-range, right-click → Delete (not "Clear contents"), then Save. Re-test the flow.
- Confirm there is only one table. In Excel: Formulas → Name Manager. Make sure only the table you’re writing to exists, and that it isn’t overlapped by another named range or a stray table on a different sheet that shares row indexes.
- Re-create the table reference. In the Add a row into a table action, re-pick the File and Table from the dropdown (don’t type the path). This forces Power Automate to resolve the current table ID via Graph and clears any stale binding.
- Switch the file to "Always open in browser" for the flow account. If the workbook is being edited concurrently by anyone (including AutoSave from another device), the action will conflict. The Excel Online (Business) connector documents these concurrency limits.
- Re-enable the flow. Once you’ve fixed the sheet, go to My flows → … → Turn on. See Disable or delete a flow for the supported re-enable steps (a flow that Microsoft disabled for failures has to be turned back on manually).
Known limits worth knowing
Per the Excel Online (Business) known issues and limitations, the connector is designed for "small Excel files (up to 25 MB)" and tables only — anything that prevents Excel from cleanly extending the table will surface as InsertDeleteConflict / "would move cells" / "resource locked" errors. Microsoft’s documented mitigation is to keep the sheet that hosts the table free of any other content below or to the right of the table, and avoid concurrent writes.
If after step 1 the issue persists, the next best test is to copy the table to a brand-new workbook, point the action at the new file, and run once — if that works, the original workbook has accumulated state Excel can’t reconcile, and the cleanest fix is to keep using the new file.
Found this helpful? Please mark ✅ "Does this answer your question?" so others searching for the same issue can find it quickly. A 👍 on "Was this reply helpful?" or a ♥ Like is also much appreciated!
Raghav Mishra — LinkedIn | PowerAI Labs
