When to use loop and when to use Workflow executor

How to decide that which approach to use when we can row b y row fetching or action.

Use Start Loop and Continue Loop when performing lightweight, single-workflow iterations within a single .psw file.

  • Best Suited For:
    • Single-file workflows: Quick row serialization where you want to keep everything inside one workflow without creating separate child files.
    • Table/Page Traversal: Iterating through web tables (using Web Loop Table) or paginating across web pages.
    • Simple counter/condition loops: Iterating a fixed number of times (Number of iterations) or evaluating dynamic in-memory conditions.

Use Workflow Executor when you want to pass input stream rows from a parent workflow to a child workflow for modular, robust processing.

  • Best Suited For:
    • Modularity & Reusability: When you want to separate data ingestion (parent) from business/GUI processing (child), allowing the child workflow to be reused across different projects.
    • Complex Multi-Step Processing: When each row requires an extensive sequence of actions, keeping the parent workflow canvas clean and readable.
    • Overcoming Loop Step Restrictions: When your row-processing logic requires steps forbidden inside loops (such as Send Email or input/file operations)