Sometimes, when updating an Excel file with Power Automate, you might notice a delay before those changes are actually visible to subsequent actions. Depending on how your flow is built, this “sync lag” can cause empty files to be sent or processed.
In this post, I share a reliable workaround to handle this synchronization issue.
The Issue: Excel Sync Lag
When updates are applied to an Excel file on SharePoint Online or OneDrive, the “save” process in the cloud can take a few moments. If your flow tries to read the file immediately after updating it, it might retrieve the old version.
- Duplicate a template Excel file on SPO
- Add data to the duplicated Excel
- Get the file content and send it via email
*Note: In a production flow, you should delete the temp file afterwards, but I omitted that step here.
The cause is simple: The “Get File Content” action runs before the Excel Online service has finished committing the updates.
The Solution: Wait for the ‘Modified’ Timestamp
ticks function) against the time captured before the loop.
Here is the expression used:
ticks(outputs('Get_file_properties')?['body/Modified'])
While this lag doesn’t happen every time, adding this logic makes your automation much more robust for production environments.
コメント