>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3571273. --> Reported by: [joevagyok](https://www.drupal.org/user/2876343) >>> <h3>Summary</h3> <p>Add a Workflow Execution Service that provides a programmatic API for executing FlowDrop workflows. This service is used internally by the Workflow Executor node but is also available for custom module development.</p> <h3>Business Value</h3> <ul> <li>Enables custom modules to trigger workflows programmatically</li> <li>Provides a clean API for workflow orchestration</li> <li>Supports integration with external systems that need to invoke workflows</li> <li>Centralizes workflow execution logic for consistency</li> </ul> <h3>Service Methods</h3> <ul> <li><code>execute()</code>: Execute a workflow with specified mode and input data</li> <li><code>getResults()</code>: Get results for an existing session with optional wait</li> <li><code>isComplete()</code>: Check if a workflow session has completed</li> <li><code>getStatus()</code>: Get the current status of a workflow session</li> </ul> <h3>Execution Modes</h3> <ul> <li><code>MODE_JOB</code>: Create session, trigger execution, wait for completion</li> <li><code>MODE_JOB_ASYNC</code>: Create session, trigger execution, return immediately</li> <li><code>MODE_JOB_FIRE_FORGET</code>: Queue for later execution (truly async)</li> </ul> <h3>Safety Features</h3> <ul> <li>Maximum execution depth of 5 levels to prevent infinite recursion</li> <li>Circular workflow reference detection using workflow chain tracking</li> <li>Parent context propagation for debugging and audit trails</li> </ul> <h3>Service ID</h3> <p><code>flowdrop_workflow_executor.service</code></p>