Autom8 AI Docs
  • Introduction to A8I
  • Quick Start
    • Your First Workflow
  • Workflows Explained
    • Create and Run a Workflow
    • Workflow Components
    • Executions
    • Manual, Partial, and Production Executions
    • Workflow Executions
    • All Executions
    • Custom Execution Data
    • Debug and Re-run Past Executions
    • Tags
    • Export and Import Workflows
    • Workflow Templates
    • Workflow Sharing
    • Workflow Settings
  • Flow Logic
  • Data
    • Data Structure
    • Data Flow Within Nodes
    • Transforming Data
    • Processing Data with Code
    • Data Mapping
  • AI Assistant
  • Glossary
  • Integrations
  • Build an AI Chat Agent in Autom8 AI
Powered by GitBook
On this page
  1. Workflows Explained

Manual, Partial, and Production Executions

Autom8 AI supports different ways to execute workflows, depending on your stage in development or deployment. Each mode offers flexibility for testing, debugging, and live automation.


Manual Executions

Manual executions are on-demand runs triggered directly from the editor. They’re ideal for testing your logic, experimenting with branching, or verifying data transformations.

Use the Test Workflow button to:

  • Run workflows ad-hoc without activating them

  • Observe real-time node outputs and flow behavior

  • Modify and rerun nodes with different inputs

Pinned Data

You can pin a node’s output to freeze its data. On future test runs, pinned nodes skip execution and reuse that data. This speeds up iteration and avoids repeated calls to external services.

Note: Pinned data is ignored in production executions.


Partial Executions

Partial executions let you test specific parts of a workflow instead of running the entire flow.

To perform one:

  • Select a node and click Run Node to execute it and any upstream nodes needed to supply input

  • Disable nodes temporarily if you want to skip services during testing

Common Troubleshooting

  • "No trigger found" error: Add a trigger node (e.g. Manual Trigger) to enable partial execution.

  • "Execution too large" error: Simplify the workflow using a Limit Node, especially if you’re testing branches with large datasets.


Production Executions

Production executions run automatically when a workflow is Active and its Trigger Node conditions are met (e.g. webhook hit, schedule match).

Steps to enable:

  • Attach a non-manual trigger node

  • Set the workflow status to Active

Once live, the workflow runs in the background. Execution logs appear in the Executions tab for review, and you can debug using the Debug in Editor feature.

Production runs do not display live inside the editor but are fully logged for analysis.

PreviousExecutionsNextWorkflow Executions

Last updated 5 days ago