Troubleshooting and FAQ
Answers to the common questions: browser support, queued runs, run errors, editing, sign-in, and what running costs.
The playground shows a compatibility warning
The playground needs a browser that supports WebAssembly JSPI. Use a recent Chrome, Edge, or Opera. Firefox users can turn it on by opening about:config and setting javascript.options.wasm_js_promise_integration to true. See the Code Playground lesson for details.
My run is queued or slow
Simulators are near-instant. Real hardware jobs are queued and processed in order, so they take longer to resolve, and a device can be offline. The Compute backends page shows which backends are simulators and which are hardware.
My run failed with a red error
The console prints a traceback pointing at the line that failed. Fix it in the editor and run again. Running on a simulator first is the quickest way to catch these before they cost anything.
I cannot edit a project
You can only edit projects you own. Edits happen on the draft, and a published project updates only when you publish your changes. See Publishing and versions.
I signed in but my work is missing
A Qollab account is tied to the provider you signed in with, Google or GitHub. Signing in with a different provider creates a separate account, so use the same one you started with.
Does running cost anything
Simulators, both local and on IonQ's cloud, are free. Only real quantum hardware uses credits. See How credits work.
Related
Stay in the loop.
Get the latest tutorials, demos, and project showcases straight to your inbox. No noise, just the good stuff.