K
kbachtold
Guest
We have some triggers that perform data maintenance on sometimes 10,000s of records. These triggers are run very rarely (in some cases only once a year per customer). However we keep fighting with the trigger timeout limit in order to get these process to run. We already have increased the timeout to 4 minutes and it isn't long enough - however we don't want to just increase this very large, because it impacts user experience for real-time UI triggers. Can some feature be added to mark a trigger as a "background trigger" that does maintenance, and whenever it is kicked off by some process (like the REST API), it runs to completion without timeout? It should also be possible to cancel the trigger from the UI in case one does go awry.
Continue reading...
Continue reading...