IssueTracker

It does look like it's impossible to reproduce with a simple use case that I specified.
We have a huge project and it would be impossible to put all the code here. Right now we are working on removing duplicate function names (even though none of them is called from a trigger) to see if it fixes it.
But in our project, the described steps stop the trigger execution in 100% of cases.

We did remove duplicate function names and the warning disappeared (see No-dups.png)
However, the problem still persists. making any change in the Edit Trigger dialog (shown in the screenshot) or making no change and just clicking on Save – stops the trigger. The trigger shows up, but never runs.
We have a project in UAT where this issue is reproducible that we can give you access to, we also have Ids of triggers that exist, but don't run if that can help:

iEEHHfBVQiqv_QBYtjKLPA
nwKoRLtnQDqn9RguCa_ABw
rUPQ6zxQMSW8ztg1SbeUQ
mvAtaKcGRqy5kn39cPNaxQ
6PuyYdGdSCimntjVkO7MgQ

We have 2 versions of the project where this is happening: UAT (Test) environment, and Production.
Please send your email address to me and I'll add you to the project.

I'm sorry, but according to the G Suite Marketplace listing details, this project is used by almost 200,000 users around the world. We can't just create a new project and unpublish this one even if we confirmed that it would fix the issue.

Also, what do you mean by 'share the code'? The project has thousands of lines of code, I can't just copy-paste them all here.
We can give you access to the project via Cloud Console, why are you saying it's not possible?

We have a reproducible case of triggers that are not running even though they exist, I provided the Ids of such triggers.

We are also working on creating a new project to check if the problem can be reproduced. Will keep you posted, please don't close the case.

Hi. My project was returning that very same behaviour.
I noticed recurrent triggers are able to run twice.
Third time gets expired and routine stops forever.

That was fixed to me as soon as I disabled Chrome V8 for that project.
So my assumption is Chrome V8 is not suited to Google Apps and still lacks maturation.

Try yourself running Apps Script Legacy to check what happens.
BTW, I'm not from Google support. Just a regular user...

Regards

We haven't even switched to V8, were thinking about it as a way to fix all the trigger issues, but will now think twice, thanks for the heads up!

Hi, we were able to reproduce this with a new very simple project (see code below).
One important thing to note: THIS CAN ONLY BE REPRODUCED IF THE PROJECT IS PUBLISHED AS A SHEETS ADD-ON.

Here are the steps we used to reproduce the problem:
1. Create 3 blank G-Sheets documents and create hourly trigger in each document via “Create Trigger” menu (see create-trigger-menu.png)
2. Make sure all triggers run, in our case they ran 5 times during 5 hours (see triggers-list.png)
3. Go to “Edit trigger” window and just press “Save” button. We did it for the first two triggers (see modify-trigger.png)
4. This caused the 2 triggers to stop and never fire again. The trigger ids are 6CFa7J1dRkeWfK4PbHAHHA and WHAd1CcdSbqeGSlO74qwxg.
The 3rd trigger is still running, id =c1et5snyQPCZJCGmCYYfKQ. See triggers-stopped.png

Please see the test add-on code below.
 

Code.gs:

 

function createTrigger ()

{

  var triggerId = ScriptApp.newTrigger("runTrigger").timeBased().everyHours(1).create().getUniqueId();

  SpreadsheetApp.getUi().alert('Trigger created Id=' + triggerId);

}

 

function removeTriggers ()

{

  removeUserTriggers();

  removeProjectTriggers();

}

 

function removeUserTriggers ()

{

  ScriptApp.getUserTriggers(SpreadsheetApp.getActiveSpreadsheet()).forEach(function (trigger) {

    if (trigger)

    {

      var id = trigger.getUniqueId();

      ScriptApp.deleteTrigger(trigger);

      SpreadsheetApp.getUi().alert('Removed User Trigge id=' + id);      

    }

  });

}

 

function removeProjectTriggers() {

  ScriptApp.getProjectTriggers().forEach(function (trigger) {

    if (trigger)

    {

      var id = trigger.getUniqueId();    

      ScriptApp.deleteTrigger(trigger);

      SpreadsheetApp.getUi().alert('Removed Project Trigger id=' + id);      

    }

  });

};

 

function runTrigger ()

{

  Logger.log ("trigger executed");

  var range = SpreadsheetApp.getActiveSpreadsheet().getRange("A1");

  var d = new Date();

  var currentTime = d.toLocaleTimeString();

  range.setValue(currentTime);  

}

 

function onOpen(e) {

  SpreadsheetApp.getUi()

      .createAddonMenu()

      .addItem('Create Trigger', 'createTrigger')

      .addItem('Remove All Triggers', 'removeTriggers')    

      .addToUi();
}

Any updates on this?

omg... not solved this yet... 14/12/2021

can't believe they just ignored this one

Oh yes, it's still an issue. All these years we have been struggling with randomly stopped triggers without the ability to recover or delete them.