Two Power Automate flows update the same Excel workbook. Each works on its own, yet some rows go missing on busy days or appear twice after a retry. Start by checking who writes to the file and when. Fixing one flow’s retry setting will leave the same workbook exposed to other writers.

List every writer to the workbook

Include flows, Office Scripts, scheduled imports and people who edit the file manually. In a UAE trading business, one flow may log a stock request while a supervisor updates approvals in the same file. Different sheets can still share a workbook. Record which processes overlap and compare their timestamps with the missing or repeated entries.

Microsoft’s Excel Online (Business) connector documentation says simultaneous file modifications from multiple clients are unsupported and describes file locking after connector use. Separate a lock or delayed write from a genuine duplicate by comparing the original request ID with the destination rows.

Give one process responsibility for writes

For a small workflow, route each request into a queue with a stable request ID, then have one process write to the workbook. Keep manual edits away from automated write periods, or use a separate input location. A concurrency setting on one flow cannot coordinate a second flow or someone editing the file. Give the writer a way to record whether a request was applied, needs retrying or requires human review.

If a write times out, the result can be uncertain. Check the stored request ID before attempting the same business action again. Design for repeated messages even with a single writer. For continuous editing or higher volumes, consider a list or database with the necessary validation and permissions, then export a report to Excel for analysis. Choose based on who needs to edit the records, required audit history and the cost of a missed update.

Rehearse a busy hour

In a test copy, send two requests close together, repeat one request ID, and simulate an interrupted write. Compare source IDs with destination IDs and check that the operator can resolve any uncertain outcome. If the flow also triggers on workbook changes, see the guide to finding self-triggering Power Automate flows.

ITZ’s Power Automate solutions service can review who writes to the workbook and how the team detects missed updates. Describe the flows and staff that share the file.

Review your Excel automation writes

Bring the workbook location, the flows that update it and a redacted example of a missing or duplicated row. Use the form to discuss a controlled write process and when to move the operational data. Review Your Excel Automation Writes