Laminar
  • Laminar
  • Platform
    • Overview
    • Getting Started
    • Advanced
      • Configurations
      • HTTP Request Batching
      • Workflow Exit Points
      • Invoke Secondary Workflows
      • Managing Notifications
    • Best Practices
    • Keywords
      • lam.resolveThenExecute
      • lam.exit
      • lam.execute
      • lam.asyncExecute
      • lam.httpRequest
      • lam.httpRequests
  • Concepts
    • Workflows
      • Global Workflow Object
    • Flows
      • Flow Types
        • HTTP Request
        • Data Transformations
      • Flow Runs
      • Supported Languages
    • API Key
    • Configurations
    • API
      • Reference
        • Workspaces
          • Issues
          • Users
          • Invitations
            • Decline
            • Accept
            • Received
            • Created
          • Workflows
          • Flows
          • Auth credentials
          • Api keys
          • Api descriptions
        • Workflow
          • Execute
            • External
          • Flows
          • Executions
        • Users
        • Flows
          • Runs
          • Versions
          • Stats
          • Recent runs
          • Read
        • Configurations
          • Properties
          • Flow credentials
          • Workspace
        • Auth credentials
        • Api descriptions
        • Api keys
        • Transform
          • Test
        • Lami
          • Public
          • Direct
        • Auth
          • Signin
          • Register
          • Refresh
          • Me
          • Users
            • Password
    • Changelog
  • External Links
    • Book a Demo
    • Playground
    • Sign In
  • Specification
Powered by GitBook
On this page

Was this helpful?

  1. Concepts
  2. Flows

Flow Runs

Learn about Flow Runs in Laminar

Overview

Flow Runs in Laminar are instances of flow executions within workflows. They manage and track the transformation and transfer of data from input to transformed data.

Flow Runs are critical for debugging integrations in Laminar. They provide logs and status updates for each execution. They also store execution details, including:

  • Start and completion timestamps to track the duration of data processing.

  • Status updates to monitor the success or failure of the operations.

  • Execution logs for JQ debugging.

  • Payloads, transformations, and responses to verify and validate the data inputs and outputs of the transformations.

PreviousData TransformationsNextSupported Languages

Last updated 1 month ago

Was this helpful?