[daniel-joica]

What changed?

build_trace_context_headers() no longer checks the EnableTraceContextHeaders feature flag, so the x-uipath-traceparent-id and x-uipath-tracebaggage headers are always sent on LLM Gateway and guardrail requests.

The flag is on in alpha, staging, com, prod, agov, pgov, dedicated/dev and dedicated/stg. It is on in gxp except for the SapSolexOrganizations segment, and off only in nst (gitops).

uipath-platform is bumped to 0.3.1. Follow-up PRs drop their use of the flag and need this release first: UiPath/uipath-agents-python#870 and UiPath/uipath-langchain-python#1198.

How has this been tested?

• Removed the flag-off tests in test_llm_trace_context.py and the flag setup in the remaining tests.
• uv run pytest in packages/uipath-platform: 2054 passed, 7 skipped (they need credentials).

Are there any breaking changes?

• Orgs where the flag was off (nst, gxp SapSolexOrganizations) now send trace context headers.

🤖 Generated with Claude Code

[Copilot]

🟢 Approval recommended

No active review issues are reported for the trace-context header change.

No open issues 🎉

What changed in this PR

Removes the EnableTraceContextHeaders feature-flag check from uipath-platform, allowing LLM Gateway and guardrail requests to include available trace context regardless of the flag. Releases version 0.3.1 to support downstream adoption.

Changes:

• Removes the flag check and updates the helper’s documentation.
• Removes flag-disabled tests and flag setup from the remaining tests.
• Bumps the package version to 0.3.1 and updates the lockfile.

File	Description
packages/​uipath-platform/​uv.lock	Updates the package version and lockfile revision.
packages/​uipath-platform/​tests/​services/​test_llm_trace_context.py	Removes flag-specific tests and setup.
packages/​uipath-platform/​src/​uipath/​platform/​chat/​llm_trace_context.py	Removes the feature-flag check and clarifies header behavior.
packages/​uipath-platform/​pyproject.toml	Bumps uipath-platform to 0.3.1.

_{Review effort: Balanced}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

🟢 Approval recommended

No active review issues were identified for the trace-context feature-flag removal and associated package version updates.

No open issues 🎉

_{Review effort: Balanced}

[daniel-joica]

QA: low-code agent with the flag removed

Ran a low-code agent from Studio Web (alpha) on the local robot, with these local branches:

• uipath-platform: this PR (no EnableTraceContextHeaders gate)
• uipath-agents: UiPath/uipath-agents-python#870 (no client-side Model run span)

The flag is not set locally, so before this change the trace-context headers wouldn't have been sent.

Result: passed. Trace 5abbd2a25a4f47fb8b0dd5e50c7fa67b:

Agent run
├── LLM call                              (client)
│   ├── Governance evaluation             (LLM Gateway)
│   ├── LLM Request Centralized Guardrail (LLM Gateway)
│   ├── Model run                         (LLM Gateway)
│   └── LLM Response Centralized Guardrail(LLM Gateway)
└── Agent output                          (client)

• Exactly one Model run, recorded by the LLM Gateway and parented to the client LLM call. The headers reached the gateway, and nothing is duplicated.
• The gateway Model run has licenseRefId, token usage and model info.