Runs
Last updated
Was this helpful?
Last updated
Was this helpful?
A run is a single execution of an agent. For example:
Each run has a unique identifier and can be accessed directly via a URL, like .
Privacy Note: Run URLs are private by default and only accessible to users within your organization. They are not publicly accessible, ensuring your data and AI interactions remain secure.
Observability: Understand how the AI is performing by tracking and analyzing its outputs over time.
Saving cost: For the same input and model versions, cached runs can be served without triggering a new LLM call, reducing costs to $0 for serving cached runs.
Fine-Tuning and distillation: Saving all runs is required for fine-tuning models and distillation processes.
WorkflowAI provides a powerful search – available under the "Runs" section – to find specific runs:
WorkflowAI provides full transparency into the interaction with the LLM. You can easily examine both the raw prompt sent to the model and the complete response received:
Navigate to any run's detail view
Click the "View Prompt" button to see the exact instructions sent to the LLM
To import a run into the playground, you can use either:
the "Try in playground" button in the run detail view, which will automatically import the run input, and the version used to generate the run.
only import the run input, by clicking on the "Try Input in Playground" button in the run detail view.
Deleting a specific run is not possible. However, you can delete all runs for a specific agent, by deleting the agent.
By default, WorkflowAI stores all runs, available in the "Runs" section. You can view a list of all runs for a specific agent, like .
Architecture: Under the hood, runs are stored in a Clickhouse database, which is optimized for handling large amounts of data, and for fast search and aggregation queries. Clickhouse also compresses data, which reduces storage costs. Learn more about Clickhouse .
You can try viewing the prompt for .
