For now, the trigger doesn't maintain the state (no way to know which file was already processed and when) but RealtimeTriggers are more stateful (always-on process), so it seems feasible to keep a state about which files have been scanned and which were updated (even if as a local cache on the Worker)
Feature description
For now, the trigger doesn't maintain the state (no way to know which file was already processed and when) but
RealtimeTriggers
are more stateful (always-on process), so it seems feasible to keep a state about which files have been scanned and which were updated (even if as a local cache on the Worker)