Flex Consumption Service Bus invocation succeeds but Host.Results request telemetry is missing

[minman0615]

Function App: bpo-sp-fn-dev
Region: East US 2
Hosting plan: Azure Functions Flex Consumption
Worker model: .NET isolated
Function runtime: 4.1052.200.26352
Function: IndexerHandoff
Trigger: Azure Service Bus

A Service Bus-triggered IndexerHandoff execution succeeds and creates all
expected Blob Storage package artifacts, but the Azure Functions Invocations
blade does not display the invocation because no corresponding Application
Insights requests/Host.Results row is generated.

Affected execution:

Job ID:
a8029dbc-02be-4e14-89ac-d02dfa292d66

UTC window:
2026-08-05T08:06:01Z through 2026-08-05T08:06:05Z

Invocation ID:
6ab24d30-7f8a-40fc-87f7-3bc56a047384

Application Insights operation ID:
44b4c46aef21415fb3b0ec670502ff1d

Host instance ID:
06789928-4386-4646-8091-86b851b6b068

Observed telemetry:

1. Function.IndexerHandoff emitted an Executing trace.
2. The isolated worker emitted a structured start trace.
3. The worker emitted a completion trace with Outcome=PackageCreated and
   PackageAttemptNumber=1.
4. Function.IndexerHandoff emitted Executed (Succeeded), Duration=2830ms.
5. No requests row exists for this operation or time window.
6. The package was successfully written to Blob Storage.

The Function App has Host.Results and Function.IndexerHandoff configured at
Information. Request telemetry is excluded from adaptive sampling. A
category-specific worker logging filter allows Information telemetry for
IndexerHandoff.

IndexerReturn, a Blob-triggered function in the same Function App, successfully
produces Host.Results requests rows and appears in the Invocations blade. For
example, IndexerReturn produced a successful requests row at
2026-08-05T08:02:02Z using the same Functions runtime version.

Please investigate why the Azure Functions host is not creating or exporting
Host.Results request telemetry for the Service Bus-triggered IndexerHandoff
function on Flex Consumption. We do not want to create synthetic
RequestTelemetry because that could duplicate host telemetry if the runtime
behavior changes.