如何停止孤立触发器 [英] How to Stop Orphaned Triggers

查看:99
本文介绍了如何停止孤立触发器的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

有趣的用例:

1. ScriptApp触发器管理的脚本1与Google网站中的图像链接关联

2.创建脚本的新实例新帐户并更新图片链接
3.删除Google网站中的容器脚本1
4.用户访问Google网站以调用脚本,但是页面被缓存指向前一个脚本1.

5.每次删除脚本运行时,错误陷阱电子邮件都会通过电子邮件发送给我。

p>

如何删除或停止这些触发器?

解决方案

安装触发器的用户可以让他们对脚本编辑器中的我的所有触发器菜单项进行操作,找到触发器并将其删除。


Interesting use case:
1. Script 1 with ScriptApp trigger management associated as an image link in a Google Site
2. Created a new instance of the script under a new account and update the image link
3. Deleted the container script 1 within the Google Site
4. A user visited the Google Site to invoke the script, but the page was cached pointing to the previous script 1.
5. The on-error trap emails are being emailed to me every time the "deleted" script runs.

How do I delete or stop these triggers?

解决方案

If you know the user that installed the trigger you could ask them to do to the "All my triggers" menu item in the script editor, find the trigger and delete it.

这篇关于如何停止孤立触发器的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆