Mismatch in orchestrator data in Azure Storage & Azure Portal

### Description
I've been having difficulty matching orchestrator data in Azure Storage & Azure Portal. Some examples
- Getting partition key from Instances table and querying the orchestrator logs where Instance ID = partition key doesn't give me result
- Azure storage has failed orchestrator instances but running a query where RuntimeStatus = 'Failed' in LogAnalytics doesn't give a result

The log analytics query I use is the one generated when you go to **function app > function > monitor > orchestrations > run query in application insights**

### Expected behavior
I can find matching orchestrators in azure storage & azure portal. Failed orchestrators are displayed as failed

### Actual behavior
I can't find orchestrator in azure portal. Failed status is not found

### Relevant source code snippets
N/A

### Known workarounds
None

### App Details

- **Durable Functions extension version (e.g. v1.8.3)**: 2.5.1
- **Azure Functions runtime version (1.0 or 2.0)**: ~3
- **Programming language used**: C#

### Screenshots
example running function not found
azure storage
azure portal

### If deployed to Azure
> We have access to a lot of telemetry that can help with investigations. Please provide as much of the following information as you can to help us investigate!

- **Timeframe issue observed**:
- **Function App name**:
- **Function name(s)**:
- **Azure region**:
- **Orchestration instance ID(s)**:
-- running and not found: d889f9c674e74d86844a82b2601175e5
-- failed and not found: 0a6b2e3e5ec74927a2df67f632fced09
- **Azure storage account name**:

> If you don't want to share your Function App or storage account name GitHub, please at least share the orchestration instance ID. Otherwise it's extremely difficult to look up information.

No source files or tests are identified. Start by comparing the provided orchestration instance IDs across Azure Storage, the portal, and the generated Log Analytics query using Durable Functions extension 2.5.1 on Functions runtime ~3; done means matching instances and failed statuses are consistently reported.

Written by the indexing model from the issue text.