Back to Vibes

Logs and Monitoring

Monitor workflow performance, troubleshoot issues, and analyze execution data using comprehensive logging and monitoring tools to ensure reliable automation.

Table of Contents

Accessing Workflow Logs

The Logs feature provides comprehensive visibility into your Vibe workflow executions, allowing you to monitor performance, troubleshoot issues, and analyze workflow behavior. This centralized logging system tracks every aspect of your Vibes from initiation to completion.

Access Steps:

  1. Navigate to the Vibes application in the Platform
  2. Click on the Logs tab
  3. You'll see a comprehensive table displaying all workflow executions

From this interface, you can view execution status, monitor progress, access detailed execution information, and analyze workflow performance patterns.

Understanding the Logs Interface

The Logs table displays comprehensive information for each workflow execution, helping you track performance and identify issues quickly.

Workflow Information

  • • Workflow Name: The name and unique identifier of the executed Vibe
  • • Scheduled Flow ID: Shows the scheduled flow ID for scheduled executions
  • • Workflow Tags: Includes workflow tags indicating execution type (Scheduled, Recurring)

Workflow Status Types

Completed

Workflow finished successfully with all steps executed

Running

Workflow is currently executing steps

Failed

Workflow encountered an error and stopped execution

Cancelled

User or system cancelled the workflow execution

Awaiting Response

Workflow is paused, waiting for user input or external response

Current Step Information

Shows the step number where the workflow currently resides or completed, helping identify progression and potential bottlenecks.

Started At Timestamp

Displays when the workflow execution began in your local timezone, useful for tracking execution patterns and timing.

Viewing Detailed Execution Information

The Details button provides in-depth information about workflow execution, essential for understanding workflow behavior, troubleshooting issues, and verifying successful operations.

Header Information

  • • Status Badge: Visual indicator of the workflow's final state
  • • Workflow Name: The name of the executed Vibe
  • • Initiated By: Email address of the user who triggered the workflow
  • • current_step: The step number where execution completed or is currently paused
  • • started_at: Precise timestamp of workflow initiation

Step Execution Log

This section provides a chronological view of each step that was executed during the workflow, allowing you to trace the complete execution path.

Step List Display

  • • Each step is numbered sequentially (1, 2, 3, etc.)
  • • Step names are displayed with descriptive identifiers
  • • Status indicators show whether each step completed successfully or failed
  • • Expandable interface allows you to drill down into specific step details

Individual Step Information

Function Name

The specific Vibe function that was executed (e.g., sendEmail, databaseExtraction)

Execution Count

Number of times this step was executed, helpful for identifying retry attempts

Specific inputs for the current step

The exact data that was passed to the step function, including processed variable substitutions

Step Outputs

The results returned by the step function, including success responses and error messages

Workflow Context

The Workflow Context section shows the complete state of the workflow during execution, including all variables, file attachments, and state information.

Context Data Includes

  • • uniqueData: File attachments, email metadata, and trigger-specific information
  • • Global variables set during execution: Setting up configuration that scheduled flows can access:
  • • Timestamp Information: Execution timing data and workflow state timestamps

Using Logs for Troubleshooting

The Logs feature is invaluable for identifying and resolving workflow issues through systematic analysis of execution data.

Identifying Failed Workflows

  • •Look for workflows with 'Failed' status to identify problematic executions
  • •Examine the step where failure occurred and review error messages in outputs
  • •Analyze input data that may have caused the failure
  • •Check context variables that might be missing or malformed

Performance Monitoring

  • •Analyze execution timing to identify slow workflows
  • •Monitor steps with high execution counts for potential loops
  • •Track peak usage periods and system load patterns
  • •Monitor patterns in step failure and retry rates

Data Flow Verification

  • •Verify that variables are being passed correctly between steps
  • •Ensure file attachments are being processed as expected
  • •Validate that API calls receive proper responses
  • •Ensure required variables are present in the workflow context

Performance Monitoring

Execution Timing

  • • Identify workflows taking longer than expected
  • • Monitor scheduled workflow reliability and consistency
  • • Track peak usage periods and system performance

Step Execution Analysis

  • • Monitor for steps with high execution counts (potential loops)
  • • Track workflows that retry steps multiple times
  • • Identify patterns in step failure rates and types

Performance Tip: Use execution timing and step counts to identify optimization opportunities and potential infinite loops before they impact system performance.

Best Practices for Log Analysis

Regular Monitoring

  • • Establish routine for reviewing workflow performance trends
  • • Catch issues before they impact users through proactive monitoring
  • • Understand usage patterns across your organization

Proactive Troubleshooting

  • • Verify new Vibes are working as expected after deployment
  • • Monitor scheduled workflows for reliability and consistency
  • • Ensure file processing workflows handle various file types correctly

Documentation and Learning

  • • Use detailed logs to understand complex workflow behavior
  • • Document successful workflow patterns for team reference
  • • Train team members on workflow troubleshooting techniques

Key Benefits of Logs and Monitoring

The Logs feature provides the transparency and insight needed to maintain reliable, efficient workflow automation while ensuring you can quickly identify and resolve any issues that arise.

Explore Step FunctionsLearn Core Concepts