Need Help.. do your time based triggers work in V8?

[aalt...@gmail.com]

I recently released a new feature in my calendar addon that offloads some long processing function to a time triggered function, which is created like this:

```
const trigger = ScriptApp.newTrigger('runBatchJob').timeBased().after(1000).create();
```

While developing, it was working all fine while we are on HEAD. After releasing to a production branch, I noticed a number of users creating the trigger but it never runs after that.

After testing it on production with a different email, I noticed that my triggers are disabled (screenshot below).

I found this bug ticket issue which says that this is a bug on the V8 runtime and this issue is not happening if I use the `DEPRECATED_ES5` runtime.

Are you running time-based triggers on your app? which runtime are you using? What other alternatives do I have to run some of my long-processing function async?

Thanks

[Adam Morris]

I can’t think of any reason why the new runtime would introduce the problem. I’ve started the issue. Let’s try and get more attention to this. 

--
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/dfc15175-a2ec-4294-b3c4-a02f5e4f5d98n%40googlegroups.com.

--

http://classroomtechtools.com

[Marko Kolombo]

I stumbled in the same issue a couple of days ago, such a big bug.

But thanks a lot for the solution, I think I'll search (or build myself) a compiler ES6 to ES5 for GAS as a temporary solution until this is solved. I will share it when ready

Just hoping they don't deprecate Rhino before fixing this, otherwise it's going to be a mess.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/CAHQVb%2BSSfDcQ59p%2B5FbL77wSJ4r%3DaAaeTGM_hZniZMuMkyd5xA%40mail.gmail.com.

[Adam Morris]

Maybe there's something that can be done with babel?

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/CALG58ADxHsEc%3D5F3tABosA67Cwu1QV-e8XVQUtKWijp%2BiGSy%2BA%40mail.gmail.com.

[Marko Kolombo]

Babel will be my first shot

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/CAHQVb%2BSyd6oU7qxOnDy0qU%2B6s5dTMnUQBSkK2NtzheZ__%3DtO6Q%40mail.gmail.com.

[Marko Kolombo]

An update, I have created yesterday an issue (not knowing of the one that was mentioned here) and I got a reply already today. Hopefully it may raise some attention from GAS developers. Maybe you can star also this one to be updated https://issuetracker.google.com/issues/175139769#comment2

[Marko Kolombo]

Ok the webapp is ready (babel based), it compiles all .gs files from one script in ES6 to another in ES5, and it also reverts the runtime to Rhino.

I can happily announce that for me this SOLVED the issue :) 

See here https://github.com/marcomow/babel-apps-script/blob/main/README.md

[Abba T]

Thanks for the input Marc.

Yes, I can confirm that after changing to the depreacted ES5 runtime, the time based trigger worked for me. 

Btw, as we are using clasp, so we are using webpack. I was originally using a webpack configuration similar to this great starter repo for clasp.

However, that is actually setup to support v8, so I had to do some changes to the babel loader to compile back the code to ES5, including polyfill and using the `babel-preset-gas` too.