ionq.simulator: BlobNotFound after SUCCEEDED job — output blob never written (microsoft.quantum-results.v2)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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, BlobNotFound9ee812ec-478f-11f1-84f4-00133bfcd0d2— Status: SUCCEEDED, BlobNotFound
Error
azure.core.exceptions.ResourceNotFoundError: The specified blob does not exist.
ErrorCode: BlobNotFound
Steps to reproduce
- Submit any valid Qiskit circuit (barriers removed) to
ionq.simulator - Wait for
SUCCEEDED - Call
job.result()→ BlobNotFound
- Dominant language
- Python
- Stars
- 160
- Forks
- 113
- Avg merge
- 6d 23h
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/azure-quantum-python
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Export types Open
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
microsoft/azure-quantum-python#650 · 1 comment ·
-
azure-quantum
Difficulty 2/5 1-3 hours Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/azure-quantum-python#416 · 3 comments ·
All issues in microsoft/azure-quantum-python
Similar issues
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/open-webui#30750 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
OpenwaterHealth/openmotion-bloodflow-app#604 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100