Execution History
View past Flow executions, conversations, and activity logs.
Execution History
Every time someone uses one of your Flows, FormWise keeps a record of it. The History page is where you go to review all past executions, browse conversations, and dig into the details of what happened during each run.
Think of it as your activity log - a complete timeline of everything your Flows have done.
[Screenshot: The main History page showing a list of recent runs grouped by Today, Yesterday, and Last 7 Days]
Executions vs. conversations
FormWise records two slightly different things in History, and it helps to know the difference:
- Executions are individual Flow runs. A form-style Flow produces one execution every time someone submits it. Each execution has a clear start, end, and a single set of inputs and outputs.
- Conversations are chatbot sessions made up of many turns. The same end user can send dozens of messages inside one conversation, and FormWise stitches them together as a single thread.
Both show up side-by-side on the History page so you can scan them together. The icon on each row tells you which is which - chatbot conversations get a sparkle icon, executions show the Flow's logo.
Conversations and executions are both tied to an end user - the person who triggered them. See Audience for more on how that identity works.
Execution logs
The main History view shows a list of every Flow run across your account. Each entry includes:
- Flow name and version - Which Flow was used and which version was active at the time.
- User - The email address (or display name) of the person who triggered the run.
- Status - The current state of the execution. You will see one of these labels:
- Completed - The run finished successfully.
- Failed - Something went wrong during execution.
- Cancelled - The run was stopped before it could finish.
- Pending - The run is queued and waiting to start.
- Running - The run is currently in progress.
- Input and output - What the user submitted and what the Flow produced.
- Timestamp - The exact date and time the run occurred.
- Error details - If a run failed, you can see the specific error message to help you understand what went wrong.
Filtering and search
When you have a lot of executions, filtering helps you find what you need quickly.
- Search by content - Type a Flow name, a snippet of what the user said, or part of an email address. The search runs across Flow names, user identities, and the first part of each input.
- Filter by Flow - The filter dropdown at the top of the list lets you scope the view to a single Flow. Pick All results to clear it.
- Filter by AI Assistant - A dedicated filter shortcut shows only your in-app AI Assistant conversations, separating them from end-user activity.
Results are grouped into time-based sections so you can scan them easily:
- Today
- Yesterday
- Last 7 Days
- Last 30 Days
- Older
Need to filter by end user or by a custom date range? Open a specific Suite and switch to its History tab. The per-Suite view adds an end-user filter and a Today / 7d / 30d / custom range picker on top of the same data.
Inspecting a single run
Click any execution to open the detail view. You get two ways to look at the same run:
Conversation view
The conversation view replays the run the way the end user experienced it. You see the user's message at the top, followed by the AI's response, any artifacts that were produced (long-form generated content, code blocks, etc.), and any errors that were surfaced. If the Flow used voice mode or attachments, those turns are rendered inline too.
This is the right view when you want to understand what the user saw.
Logs view
The logs view shows what happened under the hood. For each node in the workflow, you can see:
- Input - The data the node received.
- Output - The result the node produced.
- Duration - How long the node took to process, shown as a waterfall so you can spot the slow steps at a glance.
- Status - Whether the node succeeded or encountered an error.
- Intermediate values - The variables and JSON payloads passed between nodes, so you can trace exactly how data flowed through the workflow.
If a node failed, the logs view surfaces the full error message and any stack trace returned by the underlying provider. That is normally enough to pinpoint the cause.
[Screenshot: The execution detail view with the Logs tab open, showing a waterfall of nodes and an Input / Output panel underneath]
Debugging failed runs
The History page is one of your most powerful debugging resources. When a Flow misbehaves:
- Find the failed run in the list (filter by status if there are a lot of executions).
- Open the detail view and switch to the Logs tab.
- Scan the waterfall for the first node with an error status - that is usually where the problem started.
- Click into that node to see the exact input it received and the error it returned.
- Cross-reference with the Troubleshooting guide for common error patterns.
Once you have identified the broken node, jump back to the Flow's workflow builder, fix the issue, publish a new live version, and re-test. The next run will appear at the top of the History list.
Understanding latency and token usage
Each entry in the logs waterfall includes the duration that node took. Hover over a run in a Suite's History tab and you will also see token usage broken down by:
- Input tokens - Tokens consumed by the prompt sent to the model.
- Output tokens - Tokens produced in the model's response.
- Model - Which model handled each turn (helpful when you mix providers in one workflow).
- Cost - Shown either in credits, in USD when the run used your own API key, or as a mix of both.
Looking at these numbers over time tells you which Flows are expensive to run, which prompts are getting too long, and where you might switch to a cheaper model.
Conversations
For chatbot Flows, the History page tracks full conversation threads - not just individual runs. You can browse through the back-and-forth messages between your users and the AI, exactly as they happened.
Use the search bar to find specific conversations by their content. This is helpful when you want to locate a particular exchange or see how users are phrasing their questions.
Opening a conversation also lets you continue it - if you reply from inside FormWise, the message is sent into the same thread as if you were the AI itself. This is handy when you want to take over from the bot to answer something complex by hand.
Why history matters
The History page is more than just a log - it is one of the most valuable resources you have for improving your Flows over time. Here is how you can use it:
- Debug issues - When a Flow fails or produces unexpected output, check the execution details to see exactly which step caused the problem and what data it was working with.
- Understand your users - See what inputs people are providing, what questions they are asking your chatbots, and how they are interacting with your Flows in the real world.
- Identify patterns - Spot trends like recurring failures, popular Flows, or common user inputs that you could optimize for.
- Improve your workflows - Use real usage data to refine your prompts, adjust your logic, and make your Flows smarter and more reliable.
The more you review your history, the better your Flows become.
A note on retention
History entries persist for as long as your Flow, Suite, and organization exist. Deleting a Flow removes its executions; deleting an end user (or them clearing their browser session in the anonymous case) removes the conversations attached to that identity. There is no automatic time-based purge.