r/elixir • u/account18anni • 23h ago
Continuum v0.9.3 — durable workflows for Elixir, now with SQLite, transactional scheduling, and interval backfills
Last time I posted about Continuum here, it was at v0.8.5. Since then I’ve added a SQLite backend and a couple of scheduling features for situations that come up in real apps: saving a record that needs work later, and catching up after downtime.
Quick recap: Continuum is an OTP-native durable execution engine for Elixir. You write a workflow as ordinary Elixir and put external side effects in activities. Continuum records their results, so if the process dies or the node restarts, it can replay the workflow and pick up where it left off.
SQLite support landed in v0.9.0. You can now run durable workflows, activities, timers, signals, and recurring schedules in a single-node app without running a Postgres server. Observer and the replay tools work with SQLite too. Postgres is still the backend for clustered deployments.
Transactional scheduling builds on Continuum.Multi.enqueue/5 from the last release. Say you’re creating an invoice and want to send a reminder three days later. With Continuum.Multi.schedule_at/6, the invoice and its reminder go in the same Ecto.Multi. If the invoice rolls back, the reminder rolls back too. If the transaction commits and your app crashes on the next line, the schedule is already there for the runner to pick up.
Interval backfills solve a different problem. Suppose your nightly reconciliation uses missed: :skip. After a few days of downtime, you decide you actually need Tuesday’s and Wednesday’s runs. Continuum.Schedules.backfill/4 lets you preview that range, see which slots already exist, and pass execute: true to queue the missing ones. It respects the overlap policy, retrying the request won’t create duplicate runs, and tonight’s schedule stays where it was.
A couple of smaller changes: you can filter runs by parent or continuation chain, and pass an expected namespace when inspecting, cancelling, or pausing schedules. Both scheduling features work on Postgres and SQLite. If you’re already on v0.9.x, there’s no database migration.
Feedback is welcome, especially from anyone trying it on an existing workflow.





