Skip to content
FLOWTYPE

EXECUTION ENGINE

Run workflows reliably, and know what happens when they fail.

The execution engine runs each step in order, applies retries and timeouts, and records the result so failures are visible and recoverable.

START BUILDINGEXPLORE PLATFORM
  1. Trigger
  2. Queued
  3. Running
  4. Retry
  5. Completed

Problem

Automation fails quietly.

Scripts and point-to-point integrations often stop at the first error. Someone finds out later, when a customer or colleague asks.

  • Failures are noticed late
  • Retrying means re-running everything
  • There is no record of how far a run got

FLOWTYPE solution

Explicit behaviour for every step.

Each step has a retry policy, a timeout and an error path. A failed step can be retried on its own, without repeating the steps before it.

  • Retries with backoff (configurable)
  • Timeouts per step
  • Resume from the failed step

Product visualization

Trigger a failure, then retry it

Turn on Simulate failure and select RUN DEMO. The run stops at the failing step. Select Retry to resume from that step only.

Invoice Approval

IDLE
Run logSimulated in your browser

No executions yet. Select RUN DEMO to simulate a run.

Capabilities

What you get

  • Retries

    Automatic retries with backoff for transient errors.

  • Timeouts

    Stop steps that take longer than expected.

  • Error paths

    Route failures to a handler instead of stopping silently.

  • Run state

    Idle, running, success and failed states for every run.

  • Step history

    Input, output and duration per step.

  • Concurrency limits

    Control how many runs execute at once (planned).

Workflow example

Example: Access Request

The provisioning step fails because the directory denies the change. The engine retries, then stops and reports.

  1. 01

    Trigger

    A request is submitted and queued.

  2. 02

    Logic

    Policy is checked and approval collected.

  3. 03

    Actions

    Provisioning runs with a three-attempt retry policy.

  4. 04

    Failure

    After the final attempt the run is marked failed.

  5. 05

    Result

    The owner is notified and can retry the failed step.

  1. Access requested
  2. Check policy
  3. Manager approval
  4. Provision access
  5. Write audit entry
  6. Completed

Technical explanation

Execution model

A conceptual description of how a run progresses. Details will be documented as the engine is implemented.

  • A run is a sequence of step attempts
  • A step attempt is queued, running, then success or failed
  • The run’s state is the sum of its step states
execution.json (illustrative)Demo example
{
  "execution_id": "demo_48295",
  "status": "failed",
  "failed_step": "provision",
  "attempts": 3,
  "error": "Directory connector denied the change (demo)"
}

Continue exploring

BUILD YOUR FIRST WORKFLOW.

Turn repetitive business processes into reliable, observable workflows.

START BUILDINGEXPLORE PLATFORM