@Anneriet Krol
We've been able to reproduce this issue and I'll summarize the findings from the Azure Quantum Product team here:
In the Job Management pane, you can see that this job succeeds even though the client returns a timeout error at the 2-minute mark. This appears to be due to the Q# code where a user timeout exceeding 2 minutes (polling waiting time) is provided, however this is not respected.
To unblock yourself, please try the following steps:
- Use the
azure_quantum RE client API
, which will support Q# submission with the next QDK release. This has been checked and does not produce the timeout error. You can pre-install the next release now. - Use the azure.quantum.submit to submit a job (https://zcusa.951200.xyz/en-us/qsharp/api/iqsharp-magic/azure.submit), then wait for the result to be completed with azure.quantum.status (https://zcusa.951200.xyz/en-us/qsharp/api/iqsharp-magic/azure.status) and finally retrieve the results with azure.quantum.output (https://zcusa.951200.xyz/en-us/qsharp/api/iqsharp-magic/azure.output)
I hope this helps. If you have any questions at all, please let me know in the "comments" and I would be happy to help you. Comment is the fastest way of notifying the experts.
Please don’t forget to Accept Answer and hit Yes for "was this answer helpful" wherever the information provided helps you. This can be beneficial to other community members for remediation for similar issues.