Failed to execute action "Script": Response code 500 (Internal Server Error)

BEST CHRISTMAS PRESENT EVER: BETTER DEBUG INFO! :heart_eyes:

image

Thank you @Sergey_Truhtanov (or whoever is responsible for this) :sparkling_heart:
:smile_cat:

4 Likes

Script engine was upgraded to Nodejs 22, so feel free to use all recent apis and language features.

Editor on UI is not yet familiar with some recent Nodejs apis (like Array.flatMap for example), so you may see them underlined with red. But it should work okay. We will fix it with future releases.

1 Like


I’m running into an unhandled promise rejection error on an automation that’s been working consistently since January. When trying to trouble shoot, I’ve run into an even more puzzling problem where the script block is erroring when I add “console.”

Could this be tied to the Nodejs 22 update?

1 Like

:pensive_face:
console.log will actually work, don’t pay attention to this error in Script editor. It’s a regression issue on UI from our side, when we tried to update code editor to support Node22 features. I will fix this. But once again, it will print your output correctly, it’s just an issue on UI in js editor.

Can you please share a link to Automation that started to fail recently? Maybe via private messages here in community. Or maybe paste the script itself here if it’s possible. So I can understand how it’s related to node22 upgrade… So far we didn’t receive any complains, but maybe it’s indeed related.

1 Like