No example triggers
Check the selected chain and exact token, pool, collection, or contract address. Temporarily loosen the amount and wallet filters to see whether the selection has activity.
Examples look back over the last day. No matches can simply mean no qualifying activity in that window. If the panel is still looking, wait for it to finish; a reported lookup error is different from an empty result.
Cannot enable
The trigger needs a matching example before enabling. Review required subjects, supported selections, and filter values. If the event is rare, wait for a match or use a representative broader filter while designing; restore the intended filter before enabling.
Enabled but no run
Confirm the source supports automatic execution. NFT Transfer, Uniswap Swap, and Aave Liquidation are preview-only in this version.
Check whether a new matching event happened after enabling: old examples are not replayed. Check that the flow is Active and that every trigger filter matches.
For price and gas, inspect the latest observation, re-arm margin, and cooldown. A condition remaining true does not generate repeated alerts.
If the flow has stopped with Error, review its reason and the first failed action. Repair the configuration or connection, run a test, then re-enable it. It does not automatically restart when the issue clears.
Run exists but no message
Open the run and check whether the intended path matched. Look for the first failed action or a disconnected connection. For Slack, check channel membership; for X, inspect authorization, rate-limit, and rejection details; for a webhook, inspect the endpoint response.
If you only pressed Test run, no notification was sent. A dry preview is not a live run.
Blank values or wrong amounts
Use the event picker to check the exact path, including nested argument names. Verify that the referenced action appears earlier on the same path.
Check raw units versus decimal token amounts, optional USD values, and whether batching changed the input. Agent output is absent in dry tests.
Get help
Include the flow name, source, selected chains, approximate event time, run link if available, and expected result. Share the relevant error and a redacted example rather than credentials or private recipient data. Use the contact link in the site footer.