# IBM Runtime Diagnostic

## Account Summary

- saved account: `quantum-lab`
- saved channel: `ibm_quantum_platform`
- saved url: `https://cloud.ibm.com`
- saved instance configured: `False`
- token available to diagnostic: `True`

## Variant Results

| variant | status | elapsed seconds | backend count | backends | error |
| --- | --- | ---: | ---: | --- | --- |
| saved_default | timeout | 30.015 |  |  | timed out before Runtime service/backend discovery completed |
| saved_named | timeout | 30.016 |  |  | timed out before Runtime service/backend discovery completed |
| explicit_token_saved_url | timeout | 30.015 |  |  | timed out before Runtime service/backend discovery completed; last message: qiskit_runtime_service._discover_account:WARNING:2026-05-28 17:22:39,150: Loading account with the given token. A saved account will not be used. |
| explicit_token_platform_url | error | 0.691 |  |  | qiskit_ibm_runtime.accounts.exceptions.InvalidAccountError: 'Unable to retrieve instances. Please check that you are using a valid API token.' |

## Interpretation

- `timeout` means the Runtime client did not complete service/backend discovery within the local guard time.
- `InvalidAccountError` against `https://quantum.cloud.ibm.com` usually means the saved key is not accepted by that endpoint or account context.
- Submit QPU validation jobs only after one variant returns backend names quickly and consistently.