Skip to main content
Burst controls operate across trigger contexts. Partition the source with keyBy when each customer or record needs independent timing, or globally when every occurrence should share one timer.
automations/debounce-customer-updates.automation.ts
Each occurrence resets only its partition’s timer. Each emission creates a child context containing the selected source histories, so downstream actions can consume the burst result and inherited source values. Use collect when batch size, not time, closes the group. Use delay to resume one causal occurrence later.