I have one database trigger not firing. It was ok until this recent weekend (Sep 21, 22). It fires for one of our devs in the test environment but not for me, and not for anyone on the live version.
I’ve tried recreating the workflow from scratch but it didn’t solve the issue. Does anyone have experience solving these on their own?
I suggest you file a bug report
You could also recheck if the field or thing the database trigger is “watching” is being updated by another database trigger since database triggers can not trigger other database triggers
One database trigger event will not trigger a second one, or itself
If a database trigger has an action that makes changes to a thing, that change will not trigger a second trigger event (including the same trigger event). This could lead to an eternal loop of triggers. If you want to ensure that workflows started by a database trigger events do trigger secondary events, you can move the actions into an API workflow and schedule that workflow from the trigger workflow.
This topic was automatically closed after 14 days. New replies are no longer allowed.
