When you set up a new pipeline in TGArchiveTech, one of the first choices is how it starts: on an event, like a form submission or a record update, or on a fixed schedule, like every hour.
Event-based triggers make sense when the destination needs the data soon after it changes — a new lead going into a CRM, a support ticket routed to Slack. Waiting even ten minutes on those can mean a missed follow-up.
Scheduled triggers make more sense for aggregation work: pulling yesterday’s orders into a spreadsheet, syncing a product catalog nightly. Running that on every single change would just create noise and rate-limit issues for no benefit.
A reasonable default: if a human is waiting on the other end, use an event trigger. If a report or batch process is waiting, a schedule is usually simpler to reason about and easier to debug.