Rosetta Proposal Targets Debugging Gaps Across Drupal Workflow Systems

Developer and ECA maintainer Jürgen Haas has proposed using OpenTelemetry to connect execution records across Drupal's workflow and AI systems. In a blog post published on 28 October 2026, Jürgen outlines a shared tracing, debugging, and replay interface for the Rosetta initiative. The proposed architecture would use common execution identifiers to follow operations between Drupal modules and external automation services. No shared tracing implementation or formal adoption decision has been announced.

Drupal's workflow systems already record and inspect their own operations, but those records do not form a single execution history when systems interact. ECA captures execution steps and token values, Maestro maintains process and task records, FlowDrop records pipeline inputs and outputs, and the AI module provides logging and tracing capabilities. Jürgen also acknowledges that his Orchestration module, which connects Drupal with Activepieces, currently maintains no execution log. In a 20 October interview with The DropTimes, Jürgen had already identified the absence of a shared run record across workflow engines. His latest proposal describes the technical components that could connect those records.

The proposal identifies specific integration gaps in the Tool API, which supports Rosetta's approach to exposing reusable Drupal operations. Dries Buytaert outlined that approach in his 15 October technical account, describing how AI assistants, front-end applications and workflow systems can invoke the same tools. Jürgen reports that Maestro's tool task, FlowDrop's tool provider, WebMCP and Orchestration currently execute tool plugins directly instead of passing through the shared ToolRunner::run() method. He also identifies unused audit attachment points in the runner and missing execution context in its Invoker object. The proposal calls for these integration points to carry information about the originating run, parent step, and tracing context.

Jürgen recommends using W3C Trace Context and OpenTelemetry rather than developing a separate tracing protocol. Under his proposed approach, workflow runs and individual steps would become tracing spans, with shared context passed through tool calls, queue items, webhooks, and external services. The approach would extend existing capabilities in the OpenTelemetry module, which instruments Drupal requests, database queries and exceptions, and the AI module's provider-level tracing. Jürgen also proposes using the traceparent identifier to connect executions across system boundaries, including calls made through the Model Context Protocol. The goal is to reconstruct the sequence of operations across multiple systems without requiring administrators to examine separate execution histories.

Tracing alone would not provide the information needed to replay a workflow. Jürgen proposes a common serializer for recording step state, including ECA tokens, FlowDrop job data, and Maestro variables, while keeping large records in separate storage. He suggests pluggable storage options, including external observability systems, for installations that generate substantial execution data. The initial replay capability would focus on playing back recorded operations across systems rather than executing them again. Jürgen distinguishes this from re-execution because some actions, including sending emails and completing financial transactions, cannot be safely reversed or repeated.

Several implementation questions remain unresolved, including how to preserve tracing context across long-running workflows, record identity and access decisions, and protect personal information or secrets stored in execution histories. The proposal also calls for configurable recording policies, retention controls, and model-version information so that historical executions can be examined accurately. Jürgen argues that these decisions should be discussed before Tool API reaches its first stable release. The project released version 1.0.0-beta12 on 20 October 2026, and Jürgen's account states that a date for the proposed Rosetta Sprint had not yet been established. He is inviting discussion through the public Rosetta channel on Drupal Slack. The proposed tracing architecture remains subject to agreement among the participating projects and their maintainers.