I am also having a similar error (“The session is closed” error) when trying to run Qiskit Session using pennylane-qiskit plugins. Is there any progress?
Hi @takh2324 ,
Do you have a premium plan or a free one? The free one doesn’t allow sessions so if that’s the case you need to use job mode.
@grier_jones, we’ve been in conversations with IBM and it looks like our PennyLane developers might get access to using sessions for a couple of months starting in January. This will allow us to work on fixing the issues with qiskit_session in the plugin. In the meantime the best is to keep using Qiskit’s native Session option.
from qiskit_ibm_runtime import Session
# ...
with Session(backend=backend, max_time="25m") as session:
print(session.details())
# Your code here
# ...
I have a premium plan. However, I am experiencing a same error as @grier_jones had above which is “The session is closed” error, which occurs after single job execution.
@CatalinaAlbornoz Thanks for the update!
No problem @grier_jones .
@takh2324 the best is to keep using Qiskit’s native Session for now while we solve the issue with qiskit_session in the plugin.
We’ll keep you updated on the progress in the new year.
1 Like
This topic is temporarily closed for at least 1 hour due to a large number of community flags.
@grier_jones and @CatalinaAlbornoz , I found out you can reproduce the error by using IBM fake devices, without having IBM Premium plan. Look into this issue for the detail!
I also found out simply adding single line in pennylane-qiskit source code fixes the issue. Check this out if you still need to run Qiskit session with pennylane qiskit. I have tested it on both IBM fake devices and real hardwares (using Premium plan) and works great for me!
1 Like
Thanks for the fix @takh2324 ! This is amazing 
Our team is reviewing your fix and we’ll get back to you on GitHub.
I think this can help a lot of people.
Thanks again.
1 Like
This topic is temporarily closed for at least 1 hour due to a large number of community flags.