Stumbled into this as well. Wanting to create something similar to Fibery’s public roadmap. Including a sync for any changes that happen in the “Backend” to go to public. Selecting all the fields as triggers is not the end of the world, but i realize now that multi-relations and multi-selects can’t even act as triggers. This means that PER multi select, I’d need to add another automation.
I see that the “created date” is an option for a trigger for change (for some reason?) any chance to add “Modification date” as a trigger for a change. Then it will essentially be “trigger automation on any field”.
Unlikely, since a lot of automations make changes to the triggering entity, which will cause the modification date to change, which will (re-)trigger the automation, and so on.
I see. Unfortunate. That would just trigger a loop-detection and disable, no? How about adding multi-relations into the updating trigger?
An easier workaround I just thought of would be to make formula fields that just join the multi-relations and have those trigger. I’ll do that for the time being!