Skip to content
AIBRAINWORX / OpenSourceCoder.comLOCAL-FIRST. BUILT IN THE OPEN.
Open Source / Developer & Agent Tools

FastMCP 4.2.3 connects background traces—with a sampling tradeoff

An opt-in setting can place worker execution inside the submitting request’s trace. The default stays unchanged, and parent-based sampling can suppress a worker span when its parent was not sampled.

Listen to this articleBrowser Voice
Ready
Original diagram comparing linked background traces with an opt-in parent-child trace relationship.
OpenSourceCoder.com original explanation of versioned FastMCP telemetry documentation. Conceptual span relationships, not captured traces, execution timings or a backend we operated. · Genuine official publisher wordmark from the source recorded in the artwork credits; editorial identification, without endorsement.
Event / context: 2026-11-20 UTC. Source check: Nov 20, 2026.

FastMCP 4.2.3, released November 20, adds an opt-in way to show a background task’s execution inside the trace of the request that submitted it. The change addresses an observability problem: a tracing backend may make a worker look disconnected even when a causal link was recorded.

The default remains a separate worker trace linked back to submission. Setting parent_task_spans changes the relationship so the worker span becomes a child of the submitting context. The source retains the link as well.

The easier picture has a sampling consequence

The tagged telemetry documentation warns that a parent-based sampler then applies the submission trace’s decision to execution. A task submitted from an unsampled trace may therefore leave no recorded execution span.

This is a tradeoff in observability, not evidence that the task did not execute. Missing telemetry and missing work are different failure conditions. An operator needs to know which one the monitoring system can actually establish.

Our analysis: trace shape is part of the monitoring contract

Putting related work into one trace can make an investigation easier to follow. It can reduce the effort needed to reconstruct the relationship between a request and a later worker. That benefit is strongest when the backend’s interface does not make links easy to discover.

But a simpler view should not quietly weaken the evidence needed to investigate a failure. Before changing the relationship, a team should decide whether worker activity must remain visible independently of the sampling policy used for incoming requests.

The useful test would inspect ordinary tasks, unsampled submissions and failing workers separately. It would confirm the evidence available in the team’s actual telemetry backend rather than stopping at whether one example trace looks tidy.

Version and validation details

The implementation exposes the setting through the task extension and worker settings. The release raises the task package’s pydocket dependency to at least 0.29.1. It also changes a missing required OpenAPI path argument from a server error into a validation error and fixes several output-schema conversion cases.

Our FastMCP repository profile links the reviewed Apache-2.0 source. We did not install the release, operate a task worker or run the upstream trace tests.

Official series background

Prefect’s November 17 video discusses FastMCP 4.2 more broadly. It predates this patch and is not evidence that we tested the new tracing option.

Prefect, November 17,2026: watch the official background video.

EXPLORE THE SOURCE

GitHub repositories

Primary-source review and original editorial analysis. No software installation, model inference, paid service call, security validation or independent benchmark performed.

Follow your curiosity.

Pass the signal.