Hi Cian!
The issue you’re encountering with the “invalid workbook-session-id” can be resolved by forcing a refresh on the session ID. One way to do this is creating a new account connection:
- Create a new Microsoft account connection in Zapier. You can use the same account credentials, but setting up a fresh connection will generate a new workbook-session-id.
- After creating the new connection, re-select the spreadsheet and worksheet from the updated connection, and test the trigger again.
This should resolve the error and allow Zapier to properly pull data from your spreadsheet.
Hi,
I am encountering the same issue. I have tried both reconnecting my connection, and creating an entirely new connection. I get the same behavior. Test data shows the file being accessed correctly. But, when I try to run transfer data, I get the workbook-session-id error.
We thought it might be a microsoft two-factor authentication thing. But, we’ve run all the way through that and it did not correct the issue.
Hi @GlacierTek,
Welcome to the Community.
The "Invalid value to argument: Workbook-Session-Id" error in Zapier is likely a server-side issue from Microsoft Excel Online. To troubleshoot, try using a new spreadsheet in the root directory of OneDrive or SharePoint, avoid special characters in the spreadsheet name, clear your browser cache, and check Microsoft's server status. If the issue persists, contact Microsoft Support with detailed information for further assistance.
Let us know if this helps you solve your issue with your Zap.
Hi Jammer,
Thanks! And thank you for your reply.
I did try creating a brand new zap with a new excel file. (Cleared my cache, too). But ultimately I still get the error when I get to the “transfer data” step.
The curious thing, and Cian pointed it out in the original post, is that when creating the trigger step in my new zap, Zapier is able to access and read the excel file to display the test rows. And this behavior has been true during all the troubleshooting steps that I’ve been trying.
So I can create; run a test record; and published all successfully. But, when selecting the transfer data process, either during the create flow or once published, that’s when the error is raised.
Also to note: I can return to my new zap, open it for edit, and then request more test data. And that works (able to read the file).
Hi @GlacierTek,
Can you post a screenshot of your Zap? So we can troubleshoot further.
Hi,
I have tried both what you @PavelZ and @JammerS have suggested, each to no avail.
My current workaround for this is to copy and delete the data from my original spreadsheet to a separate one, set up and publish the Zap with access to the original (now empty) sheet, and then copy back the data to the original spreadsheet so that the Zap triggers with all the “New rows”.
This method works well for me, and seems analogous to just transferring existing data. Would be great to skip to skip the copy and paste step, so any more thoughts would be appreciated.
Thanks
Hi @Cian S,
Thank you for sharing a working resolution with this issue. This will significantly help our Community members to have as a reference for the same issue.
Hi Cian,
I’d be interested to know if your method is working as you continue to transfer records to your target (GoToWeb). When I tried to copy paste data to my source file a second time, the “new record” never triggered. I’ll note that I was actually doing a delete of my first round of transferred records, then pasting in a new batch of data.
It seems like Zapier must be caching the row number of the of the records transferred from the source file.
I was required to use a single record for testing in order to set up the zap. And then I noticed that when I copied in a batch of records, the first record of that batch was not triggered.
If you are continuing to use the zap, are you appending records to your source excel file?
Thanks,
Scott
I see this was posted only a few days ago. I’m also running into this error with a Zap and Workbook that has been working fine for well over a year now. I use ‘transfer’ as I want control over when the data populates and I had been running the update monthly to move some financial data (credit card records into Airtable).
Like the other user, testing the zap works fine, but if I try to transfer I get the error. I’ve tried getting the zap to ‘run’ by copy/pasting data but that did not help. I really don’t want to rebuild this whole workflow, I tried building a brand new zap from scratch and got the same behavior.
Perhaps one thing worth noting, the data in Excel is in a formatted table, though I don’t see why that should make a difference. Further, the data is generated by Power Query, which I initiate myself manually after downloading the latest CC transaction data from the card website.
Hi @rpiboy,
You might be running into a bug here. I would recommend reaching out to our Support Team for them to take a closer look at this issue since they have the correct tools to do so.
You can reach our Support Team here: https://zapier.com/app/get-help
I appreciate your patience and understanding.