Migrations for Durable workflow engine.

Durable requires several database tables to store workflow executions, step executions, pending inputs, and scheduled workflows.

Usage

Create a migration in your application:

defmodule MyApp.Repo.Migrations.AddDurable do
  use Ecto.Migration

  def up, do: Durable.Migration.up()
  def down, do: Durable.Migration.down()
end

Then run the migration:

mix ecto.migrate

When Durable adds new internal migrations in a future release, generate a new host-app wrapper migration:

mix durable.gen.upgrade -r MyApp.Repo
mix ecto.migrate

To check whether a database is behind the Durable library version:

mix durable.migrations -r MyApp.Repo --check

Options

• :prefix - The PostgreSQL schema name (default: "durable")
• :to - Migrate up to a specific version (inclusive)
• :step - Number of migrations to roll back (for down only)

Examples

# Default prefix - runs all pending migrations
def up, do: Durable.Migration.up()

# Custom prefix for isolation
def up, do: Durable.Migration.up(prefix: "my_app_durable")

# Rollback the last 2 migrations
def down, do: Durable.Migration.down(step: 2)

Version History

Migration versions use timestamps (YYYYMMDDHHmmss format). Use Durable.Migration.migrated_versions/1 to see applied migrations.

• 20260103000000 - Initial schema with all core tables:
  • workflow_executions - Stores workflow instances with compensation support
  • step_executions - Stores step execution history including compensation steps
  • pending_inputs - Stores pending human-in-the-loop inputs
  • scheduled_workflows - Stores cron-scheduled workflow definitions