
Please vote on this item so it might get some attention.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello
I have been using Office Scripts for a long time and never without too many issues.
One returning issue though, is that a script run in Excel Online through the Code Editor (under Automation tab), will get stuck in 'The script is running' while it is in fact not doing anything. Without exception, this happens to me when using Google Chrome. It seems Microsoft has not optimized things for Chrome users. When I use Microsoft Edge, things always worked.
However, this week I need to use some scripts again and now they won't work anymore on Microsoft Edge either. Just stays stuck on 'The script is running'. Nothing has been changed in these scripts and they worked perfectly before.
What do I do to fix this? These are business critical scripts.
Please vote on this item so it might get some attention.
Also having this issue today at my office. Doesn't work on any computer.
This feature depending on internet connection is unacceptable. VBA scripts runs locally so why not office scripts?
I ran into this issue after some days working normally since I started with Office Scripts this week. No matter if I run the script on the Desktop version, or on the web version (Edge or Chrome). The notification "The script is running..." will stay forever without actually doing any command.
Hi @Sakura , could you please try reproducing the issue then sending feedback (referencing this post) from within Excel following the instructions below? This will help us better diagnose the issue.
Not sure if there was any feedback since I last time inquired, but the issue has been popping all day now for me, meaning I cannot move forward with a project. A simple Office Script like this stays stuck on 'The script is running'. Happening on both Chrome and Microsoft Edge.
function main(workbook: ExcelScript.Workbook)
{
// Your code here
console.log("success")
}