Durable orchestration on Rails: from continuation to workflow
Rails 8.1 shipped Active Job Continuation so long-running jobs survive restarts and resume from a checkpoint. This was a real step forward, but can only be the beginning. The workflows Rails apps orchestrate today need more than interruptibility: durable state across steps, pause/resume capabilities, and human-in-the-loop-like interactions.
- ▪Rails 8.1 shipped Active Job Continuation so long-running jobs survive restarts and resume from a checkpoint.
- ▪This was a real step forward, but can only be the beginning.
- ▪The workflows Rails apps orchestrate today need more than interruptibility: durable state across steps, pause/resume capabilities, and human-in-the-loop-like interactions.
Events with Evil Martians files mainly under news. We currently carry 5 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | evilmartians.com |
| Canonical URL | https://evilmartians.com/events/rails-world-durable-orchestration-on-rails |
| Publication time | 2026-09-23T00:00:00.000Z |
| Retrieval time | 2026-07-23T15:03:04.842Z |
| Last seen | 2026-07-23T15:03:04.842Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | vAihzJJOzsPr |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Rails 8.1 shipped Active Job Continuation so long-running jobs survive restarts and resume from a checkpoint. This was a real step forward, but can only be the beginning. The workflows Rails apps orchestrate today need more than interruptibility: durable state across steps, pause/resume capabilities, and human-in-the-loop-like interactions. Building complex workflows and agentic pipelines in Rails has been simplified but still requires manual plumbing or reaching out to third-party gems or services. This talk explores the preexisting patterns and solutions to the durable workflow orchestration problem and introduces a small, principled extension to Active Job that connects the dot: same step DSL, same job runner, now with persistent context, scheduled steps, and first-class resumeability.
Excerpt limited to ~120 words for fair-use compliance. The full article is at evilmartians.com.
Discussion
0 commentsMore from evilmartians.com
