Logging
TradingGoose provides comprehensive logging for all workflow executions, giving you complete visibility into how your workflows run, what data flows through them, and where issues might occur.
Logging System
TradingGoose offers two complementary logging interfaces to match different workflows and use cases:
Real-Time Console
During manual or workspace-chat execution, logs appear in a Workflow Console widget configured for the same workflow. You can place and resize that widget anywhere in a dashboard layout.
The console shows:
- Block execution progress with active block highlighting
- Real-time outputs as blocks complete
- Execution timing for each block
- Success/error status indicators
Logs Page
All workflow executions—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
- Log retention based on the effective tier of the workspace's configured user or organization billing owner
Log Details Sidebar
Clicking on any log entry opens a detailed sidebar view showing the execution timeline, block-level details, and cost summary.
Block Input/Output
View the complete data flow for each block with tabs to switch between:
Output Tab shows the block's execution 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
- Credential-shaped values are redacted in the frozen workflow snapshot; other logged tool arguments and outputs should still be treated as potentially sensitive
Execution Timeline
For workflow-level logs, view detailed execution metrics:
- Start and end timestamps
- Total workflow duration
- Individual block execution times
- Performance bottleneck identification
Workflow Snapshots
For any logged execution, click "View Snapshot" to see the exact workflow state at execution time. The snapshot provides:
- Frozen canvas showing the workflow structure
- Block states and connections as they were during execution
- Click any block to see its inputs and outputs
- Useful for debugging workflows that have since been modified
If a stored workflow snapshot is unavailable, the snapshot view shows a "Logged State Not Found" message.
Log Retention
Log retention is configured by the effective tier of the workspace's billing owner. A finite logRetentionDays value determines when old logs are removed; a tier with no retention limit keeps logs indefinitely. Check the current Subscription settings rather than relying on fixed plan names or durations.
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 executions in real-time
For Debugging
- Always check the execution timeline to identify slow blocks
- Compare inputs between working and failing executions
- 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 Webhook notifications for real-time alerts