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, such as a recent Chrome, Edge, or Opera, or Firefox 153 or later.

My run is queued or slow

The built-in simulator is near-instant. The AWS Braket and IBM simulators load their libraries the first time you pick one in a session. The IBM ones also build a model of their device on every run, and most circuits on them slow down with more shots. Remote simulators run on IonQ's cloud and get slower as you raise the shot count. Hardware waits in a queue for its machine on top of that.

IonQ publishes no wait times or job timeout. Check status.ionq.co for whether a system is up, and Running your code for what each job state means.

My run failed with a red error

Every failure reaches you the same way: a traceback in the run console. If it points at a line in your own code, fix it and run again. If it came back from the backend, the traceback carries a name like CompilationError inside it, and Error reference lists every one of those. Running on a simulator first is the quickest way to catch problems 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.

Stay in the loop.

Get the latest tutorials, demos, and project showcases straight to your inbox. No noise, just the good stuff.