ionq.simulator: BlobNotFound after SUCCEEDED job — output blob never written (microsoft.quantum-results.v2)

Bug Report

Backend: ionq.simulator via Azure Quantum (Qiskit)
Output format: microsoft.quantum-results.v2
Workspace region: West US
azure-quantum version: 3.9.0

Description

Jobs submitted to ionq.simulator complete with status SUCCEEDED (or FAILED with QATTransformationFailed if barriers are not removed), but the output blob is never written to Azure Storage. Calling job.result(), job.get_results(), or job.get_results_histogram() all throw BlobNotFound.

Reproducible Job IDs (today, 2026-05-04)

• 1cc7ff9a-47f6-11f1-b14f-00133bfcd0d2 — Status: SUCCEEDED, BlobNotFound
• 9ee812ec-478f-11f1-84f4-00133bfcd0d2 — Status: SUCCEEDED, BlobNotFound

Error

azure.core.exceptions.ResourceNotFoundError: The specified blob does not exist.
ErrorCode: BlobNotFound

Steps to reproduce

1. Submit any valid Qiskit circuit (barriers removed) to ionq.simulator
2. Wait for SUCCEEDED
3. Call job.result() → BlobNotFound

Start by reproducing the issue with the listed ionq.simulator job IDs and the steps in the report. Compare job.result(), job.get_results(), and job.get_results_histogram() while checking the Azure Storage output referenced by the job; done means successful jobs produce a retrievable microsoft.quantum-results.v2 blob without BlobNotFound.