Midio docs
API Docs
  • Getting Started
    • Welcome
    • Quick Start Guide
  • Your First Midio App
  • Guides
    • HTTP
      • Making HTTP Requests
      • Responding to HTTP Requests
      • How to reach your own endpoints
    • Branching
    • Loops
    • Map, filter, reduce
    • Working with Data
    • Expressions
    • Building Agents
    • Debugging
    • Secrets and Environment variables
    • Convert JSON to data nodes
    • Writing tests
    • Cleaning up your flows
  • Package Manager
  • Troubleshooting
  • Reference
    • The Midio Editor
      • The Node Editor
      • User Traces
      • Traces (execution)
      • Processes
      • Log
      • Services
      • Problems
      • Function Signature
      • Data
      • Settings
    • The Midio Language
      • Nodes and execution
      • Functions and Events
        • Anonymous functions
      • Modules
      • Contexts
      • Data type
      • Local variables
      • Portals
      • Waypoint node
      • Partial function application
  • The Midio Engine
  • Built in Nodes
    • Core (std)
    • HTTP
    • LLM
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Reference
  2. The Midio Editor

Traces (execution)

PreviousUser TracesNextProcesses

Last updated 13 days ago

Was this helpful?

Every time a flow is run, an item appears in the trace history panel, containing a summary of what happened during the execution. Opening a trace shows you flame graph of the functions that has been called as part of the trace. Hovering the boxes in the flame graph will highlight the node that was called, and clicking it will jump to that node.

Which trace is selected affects which values are displayed on arrows in the node graph. If a function has been called multiple times as part of a flow/trace, or the same node called many times as part of a , then moving the slider cause us to see the value at that point in the trace.

loop