Logging

Sim provides comprehensive logging for all workflow runs, giving you complete visibility into how your workflows run, what data flows through them, and where issues might occur.

Logging System

Sim offers two complementary logging interfaces to match different workflows and use cases:

Real-Time Console

During manual or chat workflow runs, logs appear in real-time in the Console panel on the right side of the workflow editor:

The console shows:

Block progress with active block highlighting
Real-time outputs as blocks complete
Timing for each block
Success/error status indicators

Logs Page

All workflow runs—whether triggered manually, via API, Chat, Schedule, or Webhook—are logged to the dedicated Logs page:

The Logs page provides:

Comprehensive filtering by time range, status, trigger type, folder, and workflow
Search functionality across all logs
Live mode for real-time updates
7-day log retention (upgradeable for longer retention)

Clicking on any log entry opens a detailed sidebar view:

Block Input/Output

View the complete data flow for each block with tabs to switch between:

Output Tab shows the block's result:

Structured data with JSON formatting
Markdown rendering for AI-generated content
Copy button for easy data extraction

Input Tab displays what was passed to the block:

Resolved variable values
Referenced outputs from other blocks
Environment variables used
API keys are automatically redacted for security

Run Timeline

For workflow-level logs, view detailed run metrics:

Start and end timestamps
Total workflow duration
Individual block run times
Performance bottleneck identification

Workflow Snapshots

For any logged run, click "View Snapshot" to see the exact workflow state at the time of the run:

The snapshot provides:

Frozen canvas showing the workflow structure
Block states and connections as they were during the run
Click any block to see its inputs and outputs
Useful for debugging workflows that have since been modified

Workflow snapshots are only available for runs after the enhanced logging system was introduced. Older migrated logs show a "Logged State Not Found" message.

Log Retention

Free Plan: 7 days of log retention (logs are archived to cloud storage and then deleted)
Pro / Team / Enterprise Plans: Logs are retained indefinitely (no automatic cleanup)

Best Practices

For Development

Use the real-time console for immediate feedback during testing
Check block inputs and outputs to verify data flow
Use workflow snapshots to compare working vs. broken versions

For Production

Monitor the Logs page regularly for errors or performance issues
Set up filters to focus on specific workflows or time periods
Use live mode during critical deployments to watch runs in real-time

For Debugging

Always check the run timeline to identify slow blocks
Compare inputs between working and failing runs
Use workflow snapshots to see the exact state when issues occurred

Next Steps

Learn about Cost Calculation to understand workflow pricing
Explore the External API for programmatic log access
Set up Notifications for real-time alerts via webhook, email, or Slack

Common Questions

Free plans retain logs for 7 days — after that, logs are archived to cloud storage and deleted from the database. Pro, Team, and Enterprise plans retain logs indefinitely with no automatic cleanup.

Each log entry includes the run ID, workflow ID, trigger type, start and end timestamps, total duration in milliseconds, cost breakdown (total cost, token counts, and per-model breakdowns), run data with trace spans, final output, and any associated files. The log details sidebar lets you inspect block-level inputs and outputs.

No. API keys and credentials are automatically redacted in the log input tab for security. You can safely inspect block inputs without exposing sensitive values.

A workflow snapshot is a frozen copy of the workflow's structure (blocks, connections, and configuration) captured at the time of a run. It lets you see the exact state of the workflow when a particular run happened, which is useful for debugging workflows that have been modified since.

Yes. The External API provides endpoints to query logs with filtering by workflow, time range, trigger type, duration, cost, and model. You can also set up webhook, email, or Slack notifications for real-time alerts when runs complete.

Live mode automatically refreshes the Logs page in real-time so new log entries appear as they are recorded, without requiring manual page refreshes. This is useful during deployments or when monitoring active workflows.