I am having this error when I am automating my Instagram reel scheduling.
t
But whenever I open the worksheet in the browser, the make.com automation runs successfully. I don’t need to verify or authorize the flow.
Give me the permanent solution.
Welcome to the Make community!
I would delete and recreate a new connection with an account that can access the file.
If the error persists, then it’s likely a bug.
For technical issues or bugs like this, directly contacting support can often lead to a faster resolution. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing sensitive information about your account or scenario might not be suitable for an open forum discussion.
You can open a new ticket here, or if you are unable to login for some reason, you can create another new free account to access the ticketing system (which is only available to logged-in users). After submitting a new ticket, you will receive an automatic confirmation email with the subject “Ticket Created” in the subject. If you do not receive this, try sending the ticket again.
If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.
Hello - I was also running into this issue, but I believe I figured it out. I believe it has to do with your active Microsoft account during Make.com’s runtime.
The issue on my side was that I had two Microsoft accounts active: my personal Microsoft 365 account (where Make was pointing to), and my business Microsoft 365 account. However, all of my currently open Excel files at the time I was using Make.com were actually signed into my business Microsoft account. So, I opened the specific Excel that Make.com was pointing to, and switched my Microsoft account on that open Excel to my personal account, then ran the Make.com scenario again. This time, it executed successfully.
So, in summary: try opening the Excel that you have Make.com pointing to, and make sure you are actually signed into that specific Microsoft account in that specific Excel file that you’ve authorized with Make.com. In my case, I wasn’t. You might want to continue to keep that Excel file open while you run the Make.com scenarios. If necessary, sign out of any other Microsoft accounts active on your machine.
Hope that helps; I see it’s a common question in the Make.com community.