Our database triggers are not firing in any of our test branches. Still firing for our live app, but we’re afraid to push an update in case that sends it to live.
We’ve tested extensively and isolated the issue to our database triggers. Even a database trigger with no conditions on it doesn’t trigger no matter how the object it is watching is changed.
Just did a quick test after seeing your post. I have a trigger configured to send an email whenever a new thing is created, and I got an email pronto after creating a thing (in version-test).
UPDATE: This is occuring in our live application as well now. It is a bit less severe, with a roughly 66% failure rate on the triggers rather than 100% failure in our test environment.
I’ve also identified that this seems to specifically affect when there is more than one DB Trigger on the same thing in the database.
So if you have three identical DB triggers:
Trigger 1: Fires about 99% of the time.
Trigger 2: Fires about 2% of the time
Trigger 3: Fires 0% of the time.
I can’t figure out what determines that order. It definitely doesn’t seem to be the creation date of the trigger because I added a new trigger for testing, and that’s the one in position 2 firing about 2% of the time.