We're sorry, the JavaScript engine reported an unexpected error. Error code INTERNAL.

[Ken chan]

We're sorry, the JavaScript engine reported an unexpected error. Error code INTERNAL.

Getting this error again only at the trigger.

Anyone else getting the same error?

[Matěj Zíka]

Oh my god YES thank you. Actually just posted a thread on Stack Overflow because of this. It's happening to me in the last few days occasinally.

SO thread: https://stackoverflow.com/questions/67186272/google-apps-script-throwing-weird-js-errors-latery

Dne úterý 20. dubna 2021 v 22:55:40 UTC+2 uživatel ken6...@gmail.com napsal:

[Matěj Zíka]

Also an issue has been created by someone on IssueTracker: https://issuetracker.google.com/185814763

I REALLY hope this gets fixed soon, I have to manually process a lot of data every day in the last 3 days to fix things.

Dne úterý 20. dubna 2021 v 23:07:06 UTC+2 uživatel Matěj Zíka napsal:

[CBMServices Web]

Yeah I got it two times today. Re ran the operation manually and all worked fine. So something was off in the Javascript engine today.

--
You received this message because you are subscribed to the Google Groups "Google Apps Script Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-script-c...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/7cd5938b-eccc-4335-83f8-8125bdafff4an%40googlegroups.com.

[Alan Wells]

There are multiple Issue Tracker issues related to the V8 runtime failing.

The following one has been assigned to someone at Google:

https://issuetracker.google.com/issues/184664889

However,  the fact that an issue has been assigned to someone doesn't inspire confidence in me.

There are issues that are assigned to someone that are 10 years old with absolutely no indication that they will ever get fixed.

I'd think that this is an issue that would hopefully get fixed, since it literally makes many peoples apps unusable.

But I don't know.

This particular problem has been happening since at least April 7th.

That's 13 days.

So, if you trusted V8, and you can't easily revert to runtime DEPRECATED_ES5

then you've got a problem.

Problems like this with the relatively new V8 runtime may be unavoidable.

It's impossible to create something that's absolutely perfect.

But I really don't know how seriously Google takes this, or how much effort they are putting into getting it fixed.

Even if someone from Google communicated that they understand that it's a serious issue,

and they have made it a priority, I don't know how much confidence I'd have in them.