Module · Something changed in the CRM✅Knowledge checkCheck: reacting to your own data4 questions · Pass at 60%1. A workflow triggered by changes to contacts updates a contact as its last step. What happens?Nothing unusual, because a workflow cannot trigger itselfIt triggers itself, unless the fields it writes are ignoredThe second run is blocked automatically and logged as a loopIt fires once more and stops, being rate-limited per record2. What is the difference between watched_fields and ignored_fields?watched_fields applies to updates, ignored_fields to insertsThey are two names for one filter, kept for compatibilityOnly start when these change; never start when only these doOne filters which records qualify, the other which are readable3. Why does a Segment Trigger catch things a Database Change Trigger cannot?Membership is computed, so it changes with no column editedIt runs more often, so it notices changes the other one missesIt watches every table at once rather than a single named oneIt can read old_data, which the database trigger cannot reach4. “Remind me fifteen minutes before each task is due.” Which of the three time-based tools is that?A Scheduler trigger, since the point of it is a time of dayA Delay node, since it waits a fixed period before actingA Due Time trigger — the moment is stored on the recordAny of the three; for reminders they are interchangeableCheck answers← Back to Triggers — every way a workflow startsNext topic →
