In the Logs tab of any app, see how it is actually used: what people asked or submitted, how the app responded, and what feedback came back.
Chat-based apps (Chatbot, Chatflow, Agent) and Text Generator apps log conversations; Workflow apps log runs.
What Gets Logged
Logs capture real usage from every channel: the web app, the API, and apps opened from the WEB APPS list on Home. For Workflow apps, runs started by triggers are logged too.
End-user feedback (thumbs up/down and comments) is stored with the messages it refers to.
Test sessions from the app editor are excluded for Chatflow and Workflow apps (Preview and Test Run). For other app types they are listed, under the team member’s account.
Browse Logs
Each row is one conversation or one run. Most columns explain themselves, but a few deserve context:
- Title is generated from the conversation’s first message.
- End User or Account shows a session ID for web app and API usage, or the team member’s account for usage inside Dify.
- User Rate counts end users’ likes and dislikes; Op. Rate (operator rate) counts your team’s. Both aggregate across the whole conversation.
- Trigger By (Workflow apps) shows what started each run:
- WebApp: The published web app, or a call through the API
- Webhook: A webhook trigger receiving a request
- Schedule: A schedule trigger reaching its scheduled time
- Integration: An event from a connected integration
To find a conversation, search words from its messages or the end user’s session ID. To find a workflow run, search its inputs or outputs, or paste the run ID.
Inspect a Conversation
Click a row to open the full message thread. When you hover over an answer, you can:
- See its token spend and latency.
- Open the log behind it: the raw prompt, an Agent app’s tool iterations, or a Chatflow message’s node-by-node trace.
- Rate the answer as team feedback; a dislike can carry a comment explaining what went wrong. Team ratings fill the Op. Rate column, separate from end-user feedback.
- Add an annotation pairing the question with an improved reply. See Annotation System for how annotated replies take effect.
To share a log entry with a teammate, copy its link in your browser’s address bar.
Inspect a Run
For Workflow apps, click a run to open its result, its inputs and outputs with status and token totals, and a node-by-node trace that pinpoints where a run failed or slowed down.
To reproduce an issue, click Test With Params: the workflow re-runs in the editor with this run’s inputs.
Log Retention
Logs contain complete user conversations and may include sensitive information. Ensure your application complies with local data privacy regulations: publish a privacy policy and obtain user consent where required.
- Conversation logs (Chatbot, Chatflow, Agent, and Text Generator apps): retained for the duration of the active subscription.
- Workflow run logs (Workflow apps): recent runs stay on the Logs page; runs older than about three months move to monthly archives you can download as CSV files. See Download Archived Logs for details.
Download Archived Logs Professional Team
Archived runs aren’t lost: once a month, workflow run logs that have aged past about three months are packed into a monthly archive for the whole workspace, and every archived month is available for download.
Only the workspace owner and admins can download archives in Settings > Archived logs:
- Click Prepare download for the month you need. Preparation runs in the background, so you can leave the page and come back.
- When the button turns into Download, click it to save the file. A prepared download stays available for 24 hours; after that, prepare it again.
Each download is a ZIP containing CSV files that cover all workflow runs in the workspace for that month:
To pull out a single app’s history, filter by the app_id column, present in the run and app log CSVs. An app’s ID is the long identifier in its URL in Studio.
