Károly Négyesi Details Temporal Integration for Drupal Background Jobs

Long-running Drupal jobs can become difficult to recover when failures, retries, and work distributed across multiple processes enter the picture. In a blog post published by Tag1 Consulting on 8 July 2026, Károly Négyesi, edge case engineer, explains how the Temporal module handles processes that exceed the practical capabilities of Drupal’s core Batch and Queue APIs. The examples include third-party imports, search indexing, report generation, and operations across large sets of entities.

The integration separates workflow orchestration from the Drupal code that performs individual activities. Workflows define activity order, retries, and timeouts and must remain deterministic, while activities can use Drupal services and should generally be idempotent because failed calls may be retried. Temporal records activity inputs, outputs, and workflow events in durable event history, allowing an interrupted workflow to replay to its last recorded point without repeating completed activities. Heartbeats can report progress and identify activities that have stopped responding.

The module provides workflow and activity patterns, generic sequential and parallel workflows, and Drush commands for starting and interacting with processes. RoadRunner workers poll Temporal task queues, while the tag1consulting/ddev-temporalio add-on provides a Temporal server and web interface for local DDEV environments. Drupal.org lists stable release 2.1.6, released on 21 July 2026, for Drupal 11, but marks the project as minimally maintained and outside Drupal’s security advisory policy. Négyesi’s post uses drupal/temporal:^2.1 in its example setup and says a later instalment will cover the integration with Drupal’s Batch API.