Hi @Christophe_Pere ,
My colleague Austin helped me find the source of this issue.
It seems like it’s due to a difference in the version of qiskit_ibm_runtime . The latest 0.30.0 dev release seems to have broken this keyword. The documentation suggests that the keyword should still be useable but they may have broken it accidentally. You can switch to the stable release of qiskit_ibm_runtime using pip install qiskit_ibm_runtime==0.29.0 and the issue should resolve itself.
Let me know if this works for you!