github Azure/azure-sdk-for-net Azure.AI.AgentServer.Responses_1.0.0-beta.4

latest releases: Azure.ResourceManager.Hci_1.3.0-beta.1, Azure.ResourceManager.Hci.Vm_1.0.0-beta.2, Azure.ResourceManager.DataLakeAnalytics_1.1.2...
pre-release6 hours ago

1.0.0-beta.4 (2026-04-22)

Features Added

  • Foundry storage logging now includes the traceparent header (W3C distributed trace ID) in all
    log messages, enabling correlation between SDK log entries and backend distributed traces.
  • All endpoints now return the x-request-id response header for request correlation (via Core
    RequestIdMiddleware). Value is resolved from OTEL trace ID → incoming x-request-id header → GUID.
  • Error responses (ApiErrorResponse) are automatically enriched with error.additionalInfo.request_id
    matching the x-request-id response header value, enabling client-side error correlation.
  • Persistence failure resilience — when storage operations fail, responses now complete gracefully
    with status: "failed" and error.code: "storage_error" instead of crashing or leaving responses
    permanently stuck at in_progress. Covers all execution modes (streaming, background+streaming,
    background+non-streaming, synchronous). For streaming responses, terminal SSE events are buffered,
    persistence is attempted, and on failure the terminal event is replaced with response.failed
    carrying error_code="storage_error". Synchronous persistence failures return HTTP 500 with the
    storage error details.

Bugs Fixed

  • Fixed InvalidOperationException: Response was not set crash in FoundryStorageLoggingPolicy when
    a transport-level failure (DNS resolution, connection refused, timeout) occurs before any HTTP
    response is received. These failures are now logged at Error level without triggering the
    logging crash, and the original transport exception continues to propagate.
  • Fixed GetInputExpanded not normalizing string content shorthand on ItemMessage. When
    content is a plain JSON string (e.g., "Hello"), it is now auto-expanded to the canonical
    array form ([{"type":"input_text","text":"Hello"}]) so that ItemMessage.Content BinaryData
    is always consistent regardless of input format.

Other Changes

  • Removed x-ms-request-id from Foundry storage logging (unused service header).
  • Migrated header name constants to use PlatformHeaders from Core package instead of
    local private const declarations.

Don't miss a new azure-sdk-for-net release

NewReleases is sending notifications on new releases.