Future events and detection time
Enabling starts a flow from current activity; it does not backfill earlier events or the period while it was disabled. Observations and delivery take time. An alert is not a guarantee of immediate detection or complete historical coverage.
A chain can reorganize and an external service can be unavailable. Use the run result and original transaction when checking what happened. Active describes a flow’s setting, not proof of successful delivery.
High-volume flows
A flow can produce at most 500 runs in one evaluation cycle. If more events qualify, not all of them will produce a run. Do not rely on the run history to show the full number of excluded matches.
Narrow your filters or use Batch per block where supported. Batching groups matching events from one chain and block; it is not an hourly or daily digest.
History
The default retention is 30 days for detailed action requests and responses and approximately 13 months for run records. Older original events may no longer be available even while the run summary remains.
Review and save the evidence you need while it is available. A missing old payload does not mean the action sent an empty message.
Current feature boundaries
NFT Transfer, Uniswap Swap, and Aave Liquidation can be previewed but do not run automatically in this version. Token price lookup as an action, Linear actions, and Google Sheets actions are not available yet.
Post to X supports text and replies, without media attachments. Webhook signing, custom webhook headers, and an incoming webhook trigger are not offered by the current UI.
Transform has no network or persistent state between runs. It can calculate over the current input, but cannot maintain a running total across separate events.