Durable Workflow for Laravel

Durable Workflow is the embedded Laravel runtime for durable execution. Write long-running workflows as ordinary PHP, keep completed work recorded through worker restarts and application deploys, and use Laravel's queues, cache, and database as the runtime.

This package also provides the orchestration engine hosted by Durable Workflow Server. Use the PHP SDK with Server or Durable Workflow Cloud when workers need to run outside the Laravel application or across PHP, Python, and Rust.

Install

composer require durable-workflow/workflow:^2.0
php artisan migrate

For a new v2-only application, set DW_V1_ENABLED=false before the first migration. This omits the legacy v1 tables and queue watchdog. Existing applications keep v1 enabled by default so they can drain older work; do not disable it until that work is retired. Changing this setting does not drop existing tables.

Run a Laravel queue worker or Horizon to execute workflows and activities:

php artisan queue:work

For the default database queue on SQLite, failed reservation writes preserve unclaimed work after a proven rollback. See SQLite queue reservations for the supported framework versions and custom-connector boundary.

Your First Workflow

<?php

use Workflow\V2\Activity;
use Workflow\V2\Workflow;
use Workflow\V2\WorkflowStub;
use function Workflow\V2\activity;

final class GreetActivity extends Activity
{
    public function handle(string $name): string
    {
        return "Hello, {$name}!";
    }
}

final class GreetWorkflow extends Workflow
{
    public function handle(string $name): string
    {
        return activity(GreetActivity::class, $name);
    }
}

$workflow = WorkflowStub::make(GreetWorkflow::class);
$workflow->start('world');

echo $workflow->output(); // Hello, world!

Workflow code can coordinate activities, timers, signals, queries, updates, child workflows, sagas, cancellation, retries, parallel work, side effects, continue-as-new, search attributes, memo, and message streams. The runtime persists execution history so replay can resume after process or host failure without repeating completed activities.

Schedule a Workflow

use Workflow\V2\Support\ScheduleManager;

$schedule = ScheduleManager::create(
    scheduleId: 'daily-greeting',
    workflowClass: GreetWorkflow::class,
    cronExpression: '0 9 * * *',
    arguments: ['world'],
    executionTimeoutSeconds: 120,
    runTimeoutSeconds: 60,
);

Run php artisan workflow:v2:schedule-tick from Laravel's scheduler to start due occurrences. Both scheduled occurrences and ScheduleManager::trigger() use these limits. The execution timeout covers one logical execution across retries and continue-as-new. The run timeout limits each individual run and resets on continue-as-new. Each occurrence starts a new execution budget. Omit either option, or pass null, to leave that limit unset.

See schedule timeout configuration for the action format, validation and updates.

Choose a Deployment

Embedded runs remain owned by the Laravel application. Moving new work to Server or Cloud does not reinterpret existing embedded history.

Learn More

• Embedded installation
• Embedded feature guides
• Configuration reference
• Deployment modes
• Monitoring with Waterline
• Runnable Sample App

Questions and design discussions are welcome in GitHub Discussions and Discord.

Sponsors

Durable Workflow is sustained by contributors and sponsors:

• Freispace Resource Scheduling
• Translate a Book