// AI Platform Drift
Cloudflare Workers spans now include warning attributes for telemetry issues
Cloudflare developer changelog · published 2026-10-16 16:42 UTC
WHAT CHANGEDWorkers Observability now adds two span attributes when non-fatal telemetry issues occur: cloudflare.warning.type (an identifier like span_data_limit_exceeded) and cloudflare.warning.message (human-readable explanation). When a span attribute exceeds the data limit, the Worker continues executing but the oversized attribute is dropped and the warning attributes are set.
WHY IT MATTERSOversized span attributes now fail silently with diagnostic metadata instead of being silently dropped without explanation. If you are recording large payloads or request bodies as span attributes, you will now see warnings identifying which attributes were rejected and why, making instrumentation problems visible.
WHAT TO DOSearch your Workers code for ctx.tracing.enterSpan and span.setAttribute calls that record variable-length data like request bodies, webhook payloads, or user input. Check your observability dashboard for the new cloudflare.warning.type attribute to identify any existing spans hitting the data limit.
Model-reported confidence 85% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Workers - Workers Observability now surfaces warning attributes on spans for non-fatal errors +https://developers.cloudflare.com/changelog/post/2026-07-07-warning-attributes/ +Tue, 07 Jul 2026 00:00:00 GMT + +Workers Observability now attaches warning attributes to spans for non-fatal telemetry issues. These attributes help you identify instrumentation issues. +When a warning is present, both attributes are set together: + +cloudflare.warning.type — An identifier indicating the type of warning condition. +cloudflare.warning.message — A free-form, human-readable explanation of the warning condition. + +For example, recording an entire webhook payload as a span attribute can exceed the span data limit: +export default { +async fetch(request, env, ctx) { +const payload = await request.text(); + +return ctx.tracing.enterSpan("receive-webhook", (span) => { +span.setAttribute("webhook.payload", payload); +return new Response("Accepted", { status: 202 }); +}); +}, +};export default { +async fetch(request: Request, env: Env, ctx: ExecutionContext) { +const payload = await request.text(); + +return ctx.tracing.enterSpan("receive-webhook", (span) => { +span.setAttribute("webhook.payload", payload); +return new Response("Accepted", { status: 202 }); +}); +}, +}; +The Worker still returns 202 Accepted, but tracing drops the oversized attribute. The span includes cloudflare.warning.type set to span_data_limit_exceeded and a cloudflare.warning.message identifying the rejected attribute and its size. +For more information, refer to Warning attributes.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.78, needed 0.5 |
|---|---|
| triage reasoning | New observability feature adds documented span attributes and warning conditions that developers must understand to interpret telemetry correctly. |
| signals | new observability feature with documented API surface · new span attributes introduced: cloudflare.warning.type and cloudflare.warning.message · new warning condition: span_data_limit_exceeded · changes instrumentation behavior for non-fatal errors · affects how developers debug and monitor Workers |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |