Tailflow
Log inStart free
Skip to article
Browse documentation

Manage and troubleshoot

Test runs, Runs, and Activity

Understand previews, real execution results, and failure investigation.

What Test run does

Test run evaluates the flow against the most recent matching example, checks path conditions, and previews configured actions. It does not send Slack messages, emails, webhooks, or X posts.

Transform, Decode, and NFT metadata execute to provide outputs. Agent only previews its request; it does not generate a response. Later steps that depend on Agent or a published X post cannot be fully rendered in a dry run.

A preview validates the data and configuration it can see, not future delivery, service availability, or every possible event. Test runs do not consume Tailflow credits.

Email Test Run Preview
Test runDry
Path 1 · Every eventMatched
Email
ops@example.comWould send
Subject
USDC transfer
Body
125000 tokens moved
Nothing is sent during this test.
Example. A dry test shows which path matches and what Email would send. “Would send” is a preview, not a delivery confirmation.Changes stay in this example. Nothing is saved or sent.

Find a real run

Open Runs in the flow designer to inspect that flow. Open Activity for the account-wide run feed and select a run for details.

Completed means execution finished successfully. Failed means a step or condition failed. Skipped means a path or step did not execute; a nonmatching path is expected to be skipped. Running means execution is still in progress.

Run Details: Sent and Received
Run
FlowLarge USDC transfers
StatusCompleted
ChainEthereum
Credits1
Path 1 · Email · Completed
Example. Open Runs or Activity, select a run, and expand the action. Sent and Received show the request and result when retained.Changes stay in this example. Nothing is saved or sent.

Read the evidence

Inspect the path condition, action status, what was sent, and the returned result. Start with the first failure; later skipped actions often follow from it.

A completed request is evidence of acceptance at that step, not proof that a human read a message. Temporary failures can leave a flow Active; configuration faults or repeated failures can stop it with Error status. Check both the run and the flow status.

Failed Action and Skipped Steps
Run · Failed
Path 1Matched
SlackFailed
EmailSkipped
Slack
Reason
Connection is disconnected.
Select a valid connection in the Slack action, then test again.
Example. Expand the first failure before investigating skipped steps. Fix the issue on that action or its connection.Changes stay in this example. Nothing is saved or sent.

History is not permanent

Detailed sent and returned content is retained for a shorter period than the run summary. Older runs may keep status and usage information after their detailed content or original event is unavailable. Capture the run link and relevant details promptly when asking for help.