This is exactly the kind of friction that makes people wonder if their tools are working for them or against them. A user saves files to OneDrive, sets up Power Query to pull from those files, and then hits a wall: the refresh fails unless the source file is closed first. That error isn't a minor hiccup; it is a fundamental breakdown in the workflow that cloud storage promises to solve. We think this problem points to a deeper mismatch between how traditional spreadsheets handle data connections and how modern, collaborative file systems actually work.
The practical issue here is straightforward. OneDrive is designed to keep files synchronized and available, which means it often holds a lock on a file even when you are not actively editing it. Power Query, built for an era when local files were the norm, interprets that lock as a conflict. The result is a forced choice: close the source file or abandon the refresh. That might have been acceptable when data lived on a single hard drive, but it makes no sense in a world where teams share live data across devices. The user in this story is not asking for something exotic; they are asking for a tool that respects the way they actually work.
It is worth noting that the solution often recommended, saving files locally or using Excel Online, misses the point. The user chose OneDrive for a reason: accessibility, version history, and the ability to collaborate. Asking them to work around the very feature they rely on is not a fix; it is a concession that the tool has not kept up. What this tells us is that the old spreadsheet model, where data sources are static and exclusive, is creaking under the weight of modern expectations. The user should not have to choose between keeping a source file open and refreshing their queries.
This is where a more progressive approach to data management becomes essential. An AI-native spreadsheet should handle these conflicts natively, recognizing that a file in OneDrive is not necessarily in use just because it is open. It should distinguish between an active edit and a passive sync, and it should prioritize the user's intent to refresh over an arbitrary file lock. The real takeaway here is simple: if your tool forces you to close files to get work done, it is time to look for a solution that treats your data as fluid, not fragile. The technology exists to make this seamless; the question is whether your spreadsheet is ready to use it.