Few software frustrations are as quietly maddening as the one described here: a simple cut-and-paste operation that should take a second, but instead spins into a rainbow cursor and then gives up entirely. The user has done the diligence of testing this across both a PC and a Mac, which tells us this isn't a hardware quirk or a slip of the trackpad. When a core function like dragging a row or inserting a line fails consistently, and the only common thread is OneDrive, the problem stops being about user error and starts being about how Excel 365 handles file synchronization under load.
Let's be direct about what's happening: the spreadsheet isn't "timing out" because the user is slow or impatient. The likely culprit is that OneDrive is treating the file as actively in use, and Excel is waiting for a sync confirmation that never arrives cleanly. When you cut, paste, or insert rows, the app needs to update its local model and then negotiate with the cloud. If that negotiation stalls, whether due to a locked file, a paused sync, or a conflict from a previous save, the interface freezes. The fact that this followed the user from a PC to a Mac strongly suggests the issue is tied to the account or the file's sync state, not the machine sitting in front of them.
The practical takeaway here is twofold. First, check whether the file is marked as "available offline" or if it's still actively syncing. A quick fix is to open the OneDrive settings, pause syncing for a few seconds, then resume it. This forces the client to re-establish its connection to the cloud and often clears the stuck state. Second, try copying the data into a brand-new workbook, saving that locally to the desktop, and then working from there. If the problem disappears, you've isolated the issue to the original file's sync metadata. That's not a permanent solution, but it's a diagnostic step that tells you where to focus.
The deeper point is that Excel 365 has become a hybrid creature, part local application, part cloud service, and that hybrid nature introduces failure modes that traditional spreadsheets never had. When a user says "it's timing out," what they're really describing is a breakdown in that handshake between the app and the server. The fix isn't to give the software more time; it's to force a clean reconnection. So before you reset your entire workflow or migrate off a tool you otherwise rely on, try the sync pause and resume. Then test a copy of the file locally. If those steps resolve the issue, you've found your culprit. If they don't, the next move is to check for a pending update to Excel or OneDrive, because this is the kind of bug that gets patched in a point release. Either way, you're not stuck with a broken tool, you're just one diagnostic step away from understanding where the real bottleneck lives.