Skip to main content
This page lists every kind of span Elementum sends for automations, how they nest, and when each one appears. For the attributes on each span, see the attribute reference.

Span types at a glance

Every span has resource service.name = elementum and instrumentation scope elementum.
The HTTP client span is being released. See Send trace headers to other systems.

Span tree

The same tree as indented text, from a real run that continued the caller’s trace:

automation.trigger

One span each time a trigger fires. That covers record events, approvals, comments, schedules, time-relative triggers, emails, webhooks, on-demand runs, and sub-automations started by a Run Automation action. The trigger span carries no automation or run id. To find the runs it started, look at its child or linked workflow spans.

automation.workflow

One span per automation run, created when the run starts.

Parenting of the workflow span

For runs that do not continue your trace, the workflow span is intended to be a child of the trigger. In current releases it can arrive without a parent, as a second top-level span in the same trace. Use the span link or elementum.automation.execution_id to connect it to its trigger and actions.
The link from a workflow span to its trigger span carries two attributes: Some tracing UIs, including Jaeger, show links as references the span follows from, and do not display link attributes.

Action spans

One span per attempt of each action. The span name is the action type, for example send_api_request. Each retry is a separate span with a higher elementum.automation.retry_count.

Action type to span name

The span name is the action type. The label in the first column is the action as it appears when you build the automation. The span name always equals the elementum.automation.executor attribute, so you can group by either.

Elementum bookkeeping actions

Some runs include steps that Elementum adds itself. They appear as action spans with elementum.automation.system_task = true: async_automation_task_start, async_automation_task_complete, async_automation_task_failure, automation_workflow_completion, execute_workflow_callbacks. Filter them out with elementum.automation.system_task != true when you only want the steps you built.

Batched actions

Elementum can group the same action from many runs and execute them together. Update Field is commonly batched. Assign User and Assign Group use the same action and are batched the same way. A batched action still gets its own span, under its own run’s workflow span and on its own trace, with its own status. Its span differs in two ways:
  • elementum.automation.mode is batch, and elementum.automation.batch.size and elementum.automation.batch.index say how many actions ran together and where this one sat in the group.
  • The span covers the whole batch, not only this action’s share of it. Actions in the same batch therefore have almost the same duration. Small differences between them reflect their position in the batch, not the work done.

Actions without a span

Some steps have no span of their own:
  • Structural steps, such as parallel branches and their joins. The actions inside them have spans.
  • Platform jobs that are not automation runs.
A run can have fewer action spans than steps. The Elementum run history lists every step.

Run Automation and sub-automations

A Run Automation step produces one of two shapes. Which shape you get depends on how the step is configured and how Elementum runs it.

HTTP client span

One span per outbound HTTP call of a Send API Request, named after the method (GET, POST, PUT, DELETE). Kind CLIENT, parent send_api_request. A call resent after an OAuth rejection produces a second client span. Details are in The HTTP client span.

Span status

The error status has no description. Span events, including exception events, are not sent on automation spans.

Other spans you may see

A General endpoint receives AI agent spans next to automation spans, from the same environments. They have service.name = elementum too. To separate them, filter on gen_ai.operation.name. Agent, LLM call, and tool spans carry it. Automation spans never do.