> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elementum.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Attribute Reference

> Every attribute Elementum sets on automation spans, including key, type, meaning, and when the attribute is absent.

Every attribute Elementum sets on the automation spans it sends to your endpoint. Keys are listed exactly as they arrive. Attributes defined by Elementum start with `elementum.`. Standard OpenTelemetry keys are used for HTTP calls.

AI agent spans, which General endpoints also receive, have their own attributes. Those are `gen_ai.*` keys with prompts, replies, model, and token usage, plus a few `elementum.*` keys. Some `elementum.*` keys mean something different on AI spans. For example, `elementum.error.message` carries the error's text. See the [GenAI attribute reference](https://docs.elementum.io/administration/trace-forwarding/genai-attribute-reference.md).

## Conventions

* **Type** is the OTLP value type: `string`, `int` (64-bit integer), `boolean`, or `string[]` (array of strings).
* **Spans**: T = `automation.trigger`, W = `automation.workflow`, A = action span, H = HTTP client span.
* An attribute with no value is left out. It is never sent empty. "Absent when" lists the usual reasons.
* Example ids below are placeholders.

## Resource and span properties

These are set on every automation span.

| Property | Value | Notes |
| - | - | - |
| Resource `service.name` | `elementum` | The same for every Elementum span, whichever part of Elementum ran the step. A resource attribute configured on your endpoint with this key replaces it. |
| Resource `service.version` | The current Elementum platform release | Absent when no release version is set. |
| Other resource attributes | As configured | The resource attributes you added to the endpoint. Values are strings. |
| Instrumentation scope | `elementum` | No scope version. |
| Span kind | `INTERNAL`, or `CLIENT` for HTTP client spans | |
| Status | `OK`, `ERROR`, or `UNSET` | No status description is sent. |
| Trace flags | Sampled | Always. |
| Span events | None | Not sent. |

## Status and errors

| Key | Type | Spans | Meaning | Example | Absent when |
| - | - | - | - | - | - |
| `elementum.source` | string | T, W, A, H | Marks a span produced by Elementum automation tracing. | `chronicle` | On the trigger span of a run that [continued your trace](https://docs.elementum.io/administration/trace-forwarding/continue-your-trace.md). |
| `elementum.action.status` | string | T, W, A | Whether the span completed (`SUCCESS`) or failed (`FAILURE`). Matches the span status. | `SUCCESS` | Never on these spans. Not set on HTTP client spans. |
| `elementum.error.type` | string | T, W, A | The kind of failure. `com.elementum.workflow.tracing.ExecutorReturnedFailure` means the action completed and reported a failed result. `com.elementum.workflow.tracing.SpanFailureStandIn` means an error was raised. | `com.elementum.workflow.tracing.ExecutorReturnedFailure` | The span succeeded. |
| `elementum.error.message` | string | T, W, A | Short failure label. `Executor returned FAILED` or `Executor returned FAILED_WITH_TERMINAL_ERROR` for a reported failure, or the class name of the error raised. The value never contains the original error text or record data. | `Executor returned FAILED` | The span succeeded. |

`FAILED_WITH_TERMINAL_ERROR` means the action failed in a way that is not retried.

## Trigger attributes

| Key | Type | Spans | Meaning | Example |
| - | - | - | - | - |
| `elementum.automation.trigger_type` | string | T | The kind of trigger that fired. See the values below. | `RECORD_UPDATE` |
| `elementum.automation.trigger_category` | string | T | The broad family of the trigger. | `EVENT` |

### Trigger types and their category

| `trigger_type` | `trigger_category` | Typical source |
| - | - | - |
| `RECORD_CREATE`, `RECORD_UPDATE` | `EVENT` | A record is created or updated. |
| `APPROVAL_UPDATE`, `APPROVAL_CHAIN_UPDATE` | `EVENT` | An approval or an approval chain changes. |
| `ATTACHMENT_UPDATE`, `COMMENT_ADDED` | `EVENT` | An attachment changes, or a comment is added. |
| `SURVEY_RESPONSE_CREATE`, `CONVERSATION_END`, `SLACK_MESSAGE` | `EVENT` | A survey response, the end of a conversation, or a Slack message. |
| `SCHEDULE` | `SCHEDULED` | A schedule trigger. |
| `TEMPORAL` | `TEMPORAL` | A time-relative trigger. |
| `DATAMINE` | `DATAMINE` | A data mine trigger. |
| `EMAIL_INGESTION` | `EMAIL_INGESTION` | An email trigger. |
| `WEB_HOOK`, `INTEGRATION_WEBHOOK` | `ON_DEMAND` | A webhook call. |
| `ON_DEMAND`, `USER_INITIATED`, `INTERNAL` | `ON_DEMAND` | A run started on demand. Sub-automations started by Run Automation report `ON_DEMAND`. |

## Run and automation identity

| Key | Type | Spans | Meaning | Example | Absent when |
| - | - | - | - | - | - |
| `elementum.automation.execution_id` | string | W, A | Unique id of the automation run. The same on the workflow span and every action span of the run, and in the Elementum run history. | `e0000000-0000-4000-8000-000000000001` | Action outside an automation run. |
| `elementum.automation.id` | string | W, A | Id of the automation. | `a0000000-0000-4000-8000-000000000001` | Same as above. |
| `elementum.automation.workflow_id` | string | W, A | Id of the published workflow. Each published version has its own id. | `f0000000-0000-4000-8000-000000000001` | Same as above. |
| `elementum.automation.workflow_version` | string | W, A | Published version number of the workflow that ran. | `8` | Same as above. |
| `elementum.automation.workflow_name` | string | A | Name of the automation's workflow, as entered. | `Order intake` | Same as above. |
| `elementum.automation.workflow_chain` | string\[] | A | Workflow ids of the chain of automations that led to this run, ending with this run's own workflow. On-demand runs and sub-automations carry only their own id. | `["f0000000-0000-4000-8000-000000000001"]` | Empty, or the action is outside an automation run. |
| `elementum.automation.start_outcome` | string | W | `already_started` when the start request duplicated a run that was already in progress. | `already_started` | The usual case. Only set on some runs. |

The workflow span does not carry `workflow_name`. Read it from any action span of the run.

## Action attributes

| Key | Type | Spans | Meaning | Example | Absent when |
| - | - | - | - | - | - |
| `elementum.automation.executor` | string | A | The action type. Always equal to the span name. | `send_api_request` | Never. |
| `elementum.automation.task_label` | string | A | The step name given to the action. | `Call partner API` | The step has no name, or an older workflow version did not record it. |
| `elementum.automation.workflow_task_id` | string | A | Id of the step in the published workflow. Stable across runs of the same version. | `d0000000-0000-4000-8000-000000000001` | Action outside an automation run. |
| `elementum.automation.retry_count` | int | A | Attempt number of this action. `0` is the first attempt. | `0` | Never. |
| `elementum.automation.mode` | string | A | How the action ran: `single`, or `batch` when Elementum ran it together with the same action from other runs. See [Batched actions](https://docs.elementum.io/administration/trace-forwarding/span-reference.md#batched-actions). | `single` | Never. |
| `elementum.automation.batch.size` | int | A | Number of actions that ran together in the batch. | `12` | The action did not run in a batch. |
| `elementum.automation.batch.index` | int | A | Position of this action in its batch, starting at `0`. Arrival order, not a priority. | `3` | The action did not run in a batch. |
| `elementum.automation.system_task` | boolean | A | `true` on steps Elementum adds for its own bookkeeping, such as `automation_workflow_completion`. | `true` | On actions you built. It is never `false`. |
| `elementum.automation.task_execution_id` | string | A | Id of this action execution in the run history. | `b0000000-0000-4000-8000-000000000001` | Only set on some runs. |
| `elementum.automation.provider_task_id` | string | A | Elementum's internal id for this action attempt. Useful when talking to Elementum support. | `6aeb4700-bfcf-3557-8e3d-da78c2cf53d6` | Rarely. |
| `elementum.automation.provider_workflow_id` | string | A | Elementum's internal id for the run. On many runs it equals `execution_id`. | `e0000000-0000-4000-8000-000000000001` | Rarely. |
| `elementum.user_id` | string | A | The Elementum user the run executes as. The signed-in user for a run started from the app, otherwise the automation's run-as user. An id, not a name or email. | `c0000000-0000-4000-8000-000000000001` | No user is attached to the run. |
| `elementum.toe_id` | string | A | Elementum request correlation id. Give it to Elementum support to locate platform logs for this step. | `ed09dfe5-911f-429f-8c31-d851acbcead0` | No correlation id was attached. |

## Owning Object

These attributes identify the Object that owns the automation: an App, Element, Task, Table, or Service. The attribute keys use `aspect`, which is the name of that Object on the trace.

| Key | Type | Spans | Meaning | Example | Absent when |
| - | - | - | - | - | - |
| `elementum.automation.aspect_id` | string | A | Id of the Object that owns the automation. | `0a000000-0000-4000-8000-000000000001` | The automation has no owning Object. |
| `elementum.automation.aspect_type` | string | A | Type of the owning Object. | `APP_ASPECT` | Same as above. |
| `elementum.automation.aspect_name` | string | A | Display name of the owning Object. | `Incidents` | Same as above. |

## HTTP client span

> [!NOTE]
>
> The HTTP client span is being released. See [Send trace headers to other systems](https://docs.elementum.io/administration/trace-forwarding/send-trace-headers.md).

The HTTP client span uses the standard OpenTelemetry HTTP client attributes, plus two Elementum attributes. It does not carry the action, run, or error attributes above. Read those from its parent `send_api_request` span.

| Key | Type | Spans | Meaning | Example | Absent when |
| - | - | - | - | - | - |
| `http.request.method` | string | H | HTTP method. Also the span name. | `POST` | Never. |
| `url.full` | string | H | Request URL with the user name, password, and fragment removed, and every query value replaced by `REDACTED`. A query parameter without a value becomes `REDACTED`. The path and parameter names are kept. | `https://api.example.com/orders?page=REDACTED` | Never. |
| `server.address` | string | H | Host name of the request URL. | `api.example.com` | Never. |
| `server.port` | int | H | Port of the request URL. The scheme's default port when the URL has none. | `443` | Never. |
| `http.response.status_code` | int | H | Status code of the response. | `200` | No response arrived. |
| `error.type` | string | H | Why the call failed. The status code as text for a 4xx or 5xx response, `timeout` for a timeout, or the error's class name for other failures, such as a refused connection. | `503` | The call succeeded. |
| `elementum.automation.trace_header` | boolean | H | Whether **Include Trace Header** was on for this call. | `true` | Never. |
| `elementum.automation.http.resend_count` | int | H | `1` on a call resent after an OAuth rejection. | `1` | The first send. |

The span has status `ERROR` when `error.type` is set, and `UNSET` otherwise.

## Span link attributes

On the link from `automation.workflow` to its `automation.trigger`.

| Key | Type | Meaning | Example |
| - | - | - | - |
| `link.type` | string | Marks the link back to the trigger that started the run. | `probe` |
| `link.probe.trace_id` | string | Trace id of the linked trigger span. | `4bf92f3577b34da6a3ce929d0e0e4736` |

## Attributes per span

| Span | Attributes |
| - | - |
| `automation.trigger` | `elementum.source`, `elementum.action.status`, `elementum.error.*`, `elementum.automation.trigger_type`, `elementum.automation.trigger_category` |
| `automation.workflow` | `elementum.source`, `elementum.action.status`, `elementum.error.*`, `elementum.automation.execution_id`, `elementum.automation.id`, `elementum.automation.workflow_id`, `elementum.automation.workflow_version`, `elementum.automation.start_outcome` |
| Action span | `elementum.source`, `elementum.action.status`, `elementum.error.*`, and the action, identity, and owning-Object attributes |
| HTTP client span | `elementum.source` and the eight HTTP client span attributes |

## What is never an attribute

These are not sent on automation spans: organization and environment ids, record field values, request and response bodies, header values, action inputs and outputs, exception messages and stack traces, and Elementum's internal service names. See [Privacy and security](https://docs.elementum.io/administration/trace-forwarding/troubleshooting.md#privacy-and-security).

AI agent spans do carry content and error text. See [Prompt and response content](https://docs.elementum.io/administration/trace-forwarding/genai-tracing.md#prompt-and-response-content).

## Personal data

| Attribute | What it can contain |
| - | - |
| `elementum.user_id` | A user id from your organization. Not a name or email. |
| `elementum.automation.workflow_name`, `elementum.automation.task_label`, `elementum.automation.aspect_name` | Names entered in Elementum. They contain whatever was typed. |
| `url.full` | The path of the URL a Send API Request called. Query values are removed. The path is not. |

All other automation attributes are ids, fixed values, counts, or timings.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.