Good first day of the month all
Ran into an issue with Run Script (to run Office JS on an Excel Online file).
One of our flows uses this connector to grab the contents of a six column table, transform some data, then output a JSON that is used to create a CSV. Always works without a hitch.
However, we get the BadGateway error when larger files need to be processed. Usually when the table has more than 200 rows, but of course it is less about the row count and more about the amount of data that is communicated through the connector. I suspect we're the victim of an invisible cloud throttling barrier here. It seems this throttle is set very low for Run Script because a table of 600 rows cannot really be called overkill in my opinion. I further assume that Run Script uses Microsoft Graph in the backend at some point and the limitation is there.
FYI, my licenseSKU is SeededD365. I found this in the JSON of the maker portal. I assume this also impacts my performance profile.
I am looking for a solution.
- What is the data limit in Run Script?
- How can I best measure the data size before passing it through Run Script?
- Are there other ways I can parse my Excel table and create the JSON? Note that looping the table directly in Power Automate is not an option. It is too slow, and I cannot do all data transformations as I can in Javascript/Typescript.
- Microsoft uses a lot of different names for licenses. Which one is SeededD365? Is it equal to Dynamics 365?
- If I upgrade the account, do I get a better performance profile? If yes, which license gives me the best performance profile?
Thank you
