Skip to main content
Only credits purchased with a credit card or transferred to you within an organization were migrated from the legacy platform. Promotional credits (e.g., those redeemed via access codes) did not carry over and have expired.If your credits lived in an organization (purchased or transferred there), check that you’re viewing that organization. “qBraid Default” in the upper left means you’re in your default workspace. Click the organization name to open the dropdown, switch to the correct organization, and the balance will update.
Quantum jobs data was not migrated from the legacy platform. To get your old jobs data, go to Jobs on your account page and click Download Old Jobs Data. You can work with that data using the qBraid-SDK. See Legacy Jobs Retrieval for details.
Lab uses a file sync mechanism, so your files can take a few minutes to appear after you launch. Once you’re in Lab, check the file sync indicator in the bottom toolbar to see progress. You can keep working while files populate in the background; after a few minutes, your files should be fully restored.
CPU hours measure usage as (number of vCPUs) × (hours used). For example, a 2-vCPU instance for 3 hours uses 6 CPU hours; an 8-vCPU instance for 2 hours uses 16 CPU hours. See Usage Limits for more.
You’ve used all the compute hours included with your plan for this month, and you don’t have credits set up to cover the session instead. Either upgrade your subscription for a larger monthly allocation, or buy credits and turn on auto-switch to credits — both steps are needed, since credits only cover CPU sessions when auto-switch is on. Full walkthrough in Troubleshooting.
Your qBraid account has usage limits for AI chat and CPU hours. If you reach a limit, you can “switch to credits” and keep using that service. Usage is then billed in qBraid credits instead of counting against the quota. Those charges appear on your account under Transactions.
After you launch Lab, files can take a few minutes to sync. When sync finishes, refresh the Environment Manager in the sidebar and your environments should appear.If sync has completed and you’ve refreshed Environment Manager but it still says “Workspace Empty,” you don’t have any environments installed yet. Click Add in the Environment Manager, then install an environment to get started.
It means all GPU instances of that type are currently in use due to high demand. Try again later or choose another instance type.
On qBraid, you can belong to multiple organizations (e.g., courses, teams, or your own qBraid Default workspace). Credits and context are per-organization—the name in the upper left shows which organization you’re in, and switching it changes which credits and resources you see.qBraid Default is your own workspace: your own credits and work, separate from any course or other org you’ve joined. Credits here are yours (purchased or held in your name), and you have full control with no shared management. Think of it as your individual sandbox on qBraid.
API keys authenticate you with qBraid services. When you launch Lab, we check for credentials in ~/.qbraid/qbraidrc. If none are found, we prompt you to create an API key and save it there so Lab, extensions, and the qBraid-SDK work without extra setup. For more on creating and managing keys, see API Keys.
When you exhaust your CPU hours, “Launch Lab” is blocked, so it can feel like you’ve lost access to your files. Your files are still there, and you don’t need to launch Lab to get them: go to Dashboard on your account page, scroll to Usage Overview at the bottom, and click Download Files. See Download your files. To start launching again, either upgrade your plan or set up credits, as described in Troubleshooting.
No. To run jobs on IBM devices you must use your own IBM credentials. qBraid does support direct access to other leading QPUs, including Rigetti, IQM, AQT, IonQ, Pasqal, QuEra, and more. See the full list of devices on your account page.