Time limit error for Rigetti Backend

Hi,

when playing around with the Hello World: Qiskit (with Rigetti) Jupyter notebook from the sample gallery, I am running into following problem:

When using the Aspen M3 (or M2) instead of the simulator and increasing the size of the circuit, the execution fails with the message:

Result(backend_name='rigetti.qpu.aspen-m-3', backend_version='1', qobj_id='circuit-102', job_id='6c4b4d7c-a3fa-11ed-a578-00155d791a0c', success=False, results=[ExperimentResult(shots=100, success=False, meas_level=2, data=ExperimentResultData(), header=QobjExperimentHeader(qiskit='True', name='circuit-102', num_qubits='12', metadata=None))], error_data={'code': 'InvalidInputData', 'message': 'Execution timed out.  Note: time limit: 0 seconds.'})

Code snippet used to produce the error (circuit and provider definition not shown):

from azure.quantum.target.rigetti import RigettiTarget

rigetti_simulator_backend = provider.get_backend(RigettiTarget.ASPEN_M_3)

job = rigetti_simulator_backend.run((circuit), count=100)

result = job.result()
print(result)

The problem does not seem to occur for the inital circuit given in the example, but with increasing size of the circuit this error occurs more often until it basically happens always.

Looking at the Job Management Overview it seems like the Job is already failing before it is actually running, so my thought was that the time limit in the error message could not refer to the actual execution time but to a compile time limit?

But I have seen no option to increase this limit... any ideas how to do this or what else could cause this?

Thank you!

Start with the Hello World: Qiskit (with Rigetti) Jupyter notebook and the RigettiTarget backend used by provider.get_backend. Reproduce the timeout with a larger circuit, then trace job submission and result handling to determine where the zero-second limit originates. Done means the cause and supported resolution are identified and covered by an appropriate regression test or documentation update.