Hello Chinmoy Chakraborty,

The image clearly shows that IonQ and PASQAL have a red cross under the Status column, despite showing "Available" under Availability. This indicates that the providers are deployed but not properly authenticated or provisioned for job submission. Please note that your submitted job is targeting job = service.targets("quantinuum.sim.h1-1sc").submit(...)

However, service.targets("quantinuum.sim.h1-1sc") is incorrect usage. service.targets() returns a list, not a callable method. Also, the correct target IDs must match exactly what’s available in the subscription workspace. Plus, Quantinuum is set to Basic, which may not permit job submission depending on the workspace’s subscription tier or provider limitations. Even the IonQ Status is showing red which indicates registration failure or pending account setup, preventing job submission.

Could you kindly try replacing job = service.targets("quantinuum.sim.h1-1sc").submit(...)

With

target = service.target("quantinuum.sim.h1-1sc")  # or the actual available target from the workspace
job = target.submit(circuit, name="hello world-cirq-quantinuum", repetitions=100)

Also, kindly insert this in section in your code before job submission to check available targets

print("Available Targets:")
for target in service.targets():
    print("-", target.id)

This should help you choose a target that is actually enabled
Also, since your Quantinuum plan is under "Basic" which doesn't allow job submission, upgrade to Pay As You Go

Thanks for the response.

Looks like there is no 'service.target()' method in AzureQuantumService. So I tried this:

target = service.get_target("quantinuum.sim.h1-1sc")  # or the actual available target from the workspace
job = target.submit(circuit, name="hello world-cirq-quantinuum", repetitions=100)

# Print the job ID.
print("Job id:", job.job_id())

But it is giving following error:

File ~/.local/lib/python3.11/site-packages/azure/quantum/_client/operations/_operations.py:718, in JobsOperations.create_or_replace(self, subscription_id, resource_group_name, workspace_name, job_id, resource, **kwargs)
    716             pass
    717     map_error(status_code=response.status_code, response=response, error_map=error_map)
--> 718     raise HttpResponseError(response=response)
    720 if _stream:
    721     deserialized = response.iter_bytes()

HttpResponseError: (InvalidJobDefinition) Unexpected character encountered while parsing value: {. Path 'metadata.measurement_dict', line 1, position 690.
Code: InvalidJobDefinition
Message: Unexpected character encountered while parsing value: {. Path 'metadata.measurement_dict', line 1, position 690.

This is the error I was getting earlier as well.

Please advise.

Hi Chinmoy Chakraborty,

You're right, AzureQuantumService does not have a target() method and yes, using get_target() is the right low-level approach, but the error you're encountering

HttpResponseError: (InvalidJobDefinition) Unexpected character encountered while parsing value: {. Path 'metadata.measurement_dict'

is due to a known serialization issue. This typically happens when the Cirq circuit contains metadata or dictionary structures (like measurement keys) that Azure Quantum cannot translate directly into the target provider’s format. Could you kindly try switching to service.run() method instead, which handles proper circuit serialization for Cirq and supported targets like IonQ and Quantinuum. kindly try this once

job = service.run(
    program=circuit,
    repetitions=100,
    target="quantinuum.sim.h1-1sc",  # Or "ionq.simulator" if you're testing IonQ
    name="hello world-cirq-quantinuum"
)
print("Job ID:", job.id)

Also, double-check your circuit for any unnecessary metadata or complex measurement structures. Let me know how this goes. Thanks

Hello Chinmoy Chakraborty, is your issue resolved? If not, I've requested few details from you in private message. Kindly furnish those so that we can have a look at your environment from backend. Please reply in private message only as the requested details are sensitive information. Thanks

Tried the code you mentioned but got same error.