Run Log

The Run Log is your window into the execution of your flows, providing real-time insights into how your automation is performing. Whether you’re testing a new flow or troubleshooting an issue, the Run Log gives you visibility into each step of the execution process, helping you understand what’s happening behind the scenes.

​

Understanding the Run Log

When you run a flow in Gumloop, a Run Log automatically appears, displaying the status of each node as it executes. This log provides crucial information including:

• Execution status (Success/Error) of each node
• Time taken by each node to execute
• Credit cost per node
• Access to all inputs and outputs for debugging

Important: Your workbook must be saved to track run history. Unsaved workbooks will still show the current run log, but previous runs may not be recorded properly until the workbook is saved.

​

Run Log Components

​

1. Execution Status Indicator

Each node in your Run Log includes a status indicator:

• Success: Node executed successfully
• Error: Node failed during execution
• Running: Indicated by the running clock

​

2. Time and Credit Information

For each node or subflow, you’ll see:

• Execution time: How long the node took to run (e.g., “6.18s”)
• Credit cost: Number of credits consumed by the node

At the bottom of the Run Log, you’ll find a summary showing:

• Total execution time: Total time taken by the entire flow
• Total credits consumed: Sum of credits used by all nodes

​

Viewing Inputs and Outputs

One of the most powerful features of the Run Log is the ability to inspect what data is passing between nodes. This is invaluable for debugging and understanding your flow’s behavior.

​

How to View Inputs and Outputs

1. Click the “See all inputs and outputs” button for any node in the Run Log
2. A modal will appear showing:
   • All input data the node received
   • All output data the node produced

​

Understanding the Data Display

The inputs and outputs are displayed according to their data types:

• Text: Shown as plain text
• Lists: Displayed with item counts and expandable to see all entries
• Files: Shown with file names

This modal is particularly useful for:

• Verifying that data is being passed correctly between nodes
• Checking that text formatting is as expected
• Ensuring list items contain the expected values
• Confirming that files are being processed properly

​

Working with Subflows in the Run Log

Subflows have special behavior in the Run Log that helps you debug complex workflows.

​

Navigating Subflow Execution

When a flow contains subflows, the Run Log provides two levels of visibility:

1. Parent Flow View: Shows the subflow as a single node with its overall status
2. Subflow Detail View: If you click on the subflow node you’ll see a View Run option to view the individual subflow run.

​

How to Navigate Between Parent Flow and Subflow

To inspect a subflow’s execution:

1. Click on the subflow node in the Run Log
2. Click “View Run” to see the detailed subflow execution
3. Once you’re viewing the subflow run, you can return to the parent flow by clicking on the flow tabs at the bottom of the screen

This navigation allows you to:

• See how data flows through different levels of your automation
• Pinpoint exactly where issues occur in complex workflows
• Debug each component of your flow independently

​

Loop Mode in the Run Log

When nodes run in Loop Mode, the Run Log helps you monitor the processing of multiple items.

​

Viewing Loop Mode Execution Details

In Loop Mode, the Run Log enumerates each item being processed individually:

1. Expand the node or subflow in the run log to see each individual iteration
2. Each iteration is numbered (1, 2, 3, etc.) to help you track specific items
3. You can view the inputs/outputs for any specific iteration

​

Common Loop Mode Issues

One of the most common errors you might encounter with Loop Mode is a list size mismatch. This happens when your node receives multiple list inputs of different lengths. For detailed information about diagnosing and fixing list size mismatches, see the List Size Mismatch Errors guide.

​

Reviewing Previous Runs

The Run Log keeps a history of your flow executions, allowing you to:

1. Review Previous Runs: Access past executions from the “Previous Runs” tab
2. Compare Performance: Check how changes affected execution time and results
3. Share Debugging Info: Use the Run link to help troubleshoot with teammates

Remember: To access run history, your workbook must be saved. Unsaved changes to a workbook won’t affect existing run logs, but the workbook must be saved initially to begin tracking runs.

​

Debugging Using the Run Log

​

Common Error Types in the Run Log

Error Type	How It Appears in Run Log	Common Solution
Authentication Error	”Failed to authenticate” or “Credentials not found”	Check credentials in Credentials settings
Empty Input	”No input provided” or “Input is required”	Ensure previous nodes are outputting data as expected

​

Effective Debugging with the Run Log

1. Check node status: Identify which nodes succeeded and which failed
2. Inspect inputs and outputs: Use the input/output modal to see exactly what data is passing between nodes
3. Review error messages: Look for specific error information in the node outputs
4. Trace data flow: Use the Run Log to follow how data changes as it moves through your flow
5. Analyze subflow execution: For complex flows, drill down into subflow runs to isolate issues

​

Run Log Best Practices

1. Test with small samples: Run flows with limited data first to quickly identify issues
2. Use Error Shield: Wrap critical nodes in Error Shield nodes to see both success and failure paths
3. Check previous runs: Compare current run with previous successful runs to identify changes
4. Note credit costs: Monitor credit usage to optimize efficiency
5. Save your workbook: Ensure your workbook is saved to preserve run history for troubleshooting

​

Summary

The Run Log is your most important tool for understanding, debugging, and optimizing your Gumloop flows. By effectively using the inputs/outputs modal and understanding how to navigate subflow runs, you can:

• Quickly identify and resolve issues
• Understand how data moves through your flow
• Optimize performance and credit usage
• Document and share results with your team

For more complex debugging scenarios or persistent issues, you can always reach out to the Gumloop community on forum.gumloop.com for additional assistance.