Error code registry

Check the Job, it is not valid to run on this backend.

Ensure your quantum circuit is valid and well-formed. Verify that the quantum backend you are targeting supports the operations and circuit structure you are attempting to run. Some operations might not be natively supported or require specific transpilation settings. Experiment with different optimization_level settings during transpilation. A higher level might be too aggressive for certain circuits or backends, while a lower level might not be sufficient. Very large or complex circuits can sometimes lead to transpilation difficulties, especially if the target backend has limited resources. Consider simplifying the circuit if possible. Ensure you are using a compatible and up-to-date version of Qiskit.

Use another backend to run the job.

Use another backend with basis gates.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Verify that the correct backend name was specified. To view the backends you have access to, you can either view a list on the Compute resources page, or you can use the QiskitRuntimeService.backends() method.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Use another backend to run the job. To view the backends you have access to, you can either view a list on the Compute resources page, or you can use the QiskitRuntimeService.backends() method.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

You may need to regenerate your token. Try again or contact support.

Verify your credentials and try again.

Reduce request rate and try again.

Remove some tags and try again.

Remove some characters from the tags and try again.

You need to ensure that the image name is always accompanied by its corresponding tag in the format image_name:tag.

Should be one of critical, error, warning, info or debug.

Check the JSON schema.

Access to IBM Quantum services, including specifying runtime parameters, is controlled by the instances and associated roles within those instances you are assigned to. To address this, you'll need to contact your account manager or an administrator with sufficient permissions within your IBM Quantum account and request that they grant you the necessary access.

Make sure you use a valid program name, such as sampler or estimator. Qiskit Runtime no longer supports the backend.run interface. Refer to the Migration guide for instructions to migrate to the primitives.

Pass session time greater than or equal to job time.

Your IBM Cloud account might not have the required IAM policies or roles assigned to run programs on the IBM Quantum Platform.

Use a different backend that is available on the channel.

Use a different backend.

Increase the session max_time if possible, or keep session active by reducing the time between jobs. For details, see the Session length guide.

Contact account administrator to increase limit.

Your IBM Quantum API token might be incorrect, expired, or revoked. Log in to IBM Quantum Platform website and navigate to your account settings to generate a new API token. Use QiskitRuntimeService.save_account(APIKEY, overwrite=True) to save the new API key, overwriting any outdated or incorrect credentials.

The image parameter should be in the format image_name:tag. Double-check that you're including both the image name and the tag, separated by a colon. The image_name or tag might not exist or might be incorrectly specified. Contact IBM Quantum support to confirm your authorization to use the specified image.

Incorrect parameter format or types. Check the expected format. Verify data types. Missing required parameters. Invalid parameter values. Backend limitations. Try again or contact support.

Try again or contact support.

Try again or contact support.

Try again or contact support.

You might not have an active IBM Quantum service plan associated with your account, or the plan may have expired. Some plans might have limitations on the types or numbers of backends accessible. The specific backend you are attempting to use might not be included in your current service plan. Try again or contact support.

The backend might be temporarily offline due to an unexpected issue or for unscheduled maintenance. Ensure that the backend name you are using is spelled correctly. Try again or contact support.

Check that the provided ID is unique or delete the job and try again.

Delete completed jobs and/or wait for other clients to delete jobs.

Try again later.

Try again when job has reached a terminal state.

Try again or contact support.

Double-check the CRN on the instance page. If the specified CRN is correct, contact support.

Specify the instance allocation in seconds.

Verify the service plan ID.

Verify the backend and service plan ID.

The specific backend or QPU you're trying to use might be offline for maintenance, upgrades, or due to operational issues. There might be limits on the number of active jobs allowed per backend, and if this limit is reached, jobs might be rejected or queued with a timeout. Intermittent network problems between your environment and the IBM Quantum Platform can disrupt the queuing process. Jobs exceeding a certain time threshold. If your job involves features not supported by the specific backend or service plan. Specifying incompatible options or using dynamic circuits with V2 Estimator might also lead to this error. Pulse gates are no longer supported. If your program uses them, you'll need to migrate to fractional gates. Try again or contact support.

Verify that the account and plan ID are correct.

Submit the job to a backend that is included in your plan.

Contact the instance administrator to increase the allocation.

Very large circuits or those with excessive depth can cause preprocessing errors. Ensure the number of shots is within the allowed range. Ensure both the code generating the job and the environment running it use the same, preferably latest, version of Qiskit. Try again or contact support.

Verify that the request included the right parameter types.

Ensure the request fields and data types are correct, or contact support for assistance.

Choose a value greater than zero.

Confirm the correct CRN or service instance name for the instance you intend to use. Ensure that the provided CRN matches the format required by Qiskit Runtime. Confirm that your IBM Cloud API key or IBM Quantum API token is correct and properly configured when initializing the QiskitRuntimeService instance. Log in to your IBM Quantum Platform account and verify that the instance is active. Try again or contact support.

Consult the Qiskit Runtime REST API documentation for information on updating instance configurations and ensure that your request conforms to the expected JSON schema and parameter types. Double-check the values provided for each parameter in your update request to ensure they are valid and in the correct format. Remove any parameters from your request that are not documented as supported by the Qiskit Runtime instance configuration update API. Verify that your request includes all mandatory fields necessary for a successful instance configuration update. Ensure your internet connection is stable and there are no network disruptions or firewalls blocking communication with the IBM Quantum Platform. Ensure your local Qiskit installation and its dependencies are compatible with the Qiskit Runtime environment. Try again or contact support.

Pass a valid instance limit.

Ensure your IBM Cloud API key or IBM Quantum API token is correct and up-to-date. Check your IBM Quantum account for any permissions restrictions that might be preventing job retrieval. Ensure your internet connection is stable and there are no firewalls or proxies blocking access to the IBM Quantum Platform. Consult the IBM Cloud Status page and IBM Quantum service alerts for any reported outages or issues affecting the Qiskit Runtime service. If you are retrieving a specific job, verify that the job_id is correct. Make sure your local Qiskit installation is compatible with the Qiskit Runtime environment. Try again or contact support.

Ensure your internet connection is stable and there are no firewalls or proxies blocking access to the IBM Quantum Platform. Consult the IBM Cloud Status page and IBM Quantum service alerts for any reported outages or issues affecting the Qiskit Runtime service. Ensure your QiskitRuntimeService is correctly initialized with valid IBM Cloud or IBM Quantum credentials (API key or token). Make sure your local Qiskit installation and its dependencies are compatible with the Qiskit Runtime environment. Try again or contact support.

Ensure your IBM Cloud API key or IBM Quantum API token is correct and up-to-date. Ensure your internet connection is stable and there are no firewalls or proxies blocking access to the IBM Quantum Platform. Consult the IBM Cloud Status page or the IBM Quantum service alerts for any reported outages or issues affecting the Qiskit Runtime service. If you are retrieving a specific job, verify that the job_id is correct. Make sure your local Qiskit installation is compatible with the Qiskit Runtime environment. You might need to update or downgrade specific packages, particularly if facing QPY format version errors. Try again or contact support.

Use a different instance.

Specify a valid instance usage allocation or contact support.

Verify the job ID is correct and that you have the correct access permissions.

There is no solution available for this issue.

You might be using an expired or incorrect API token for accessing the IBM Quantum platform. The data you're sending in your request might not conform to the expected format (e.g., incorrect JSON syntax). Your request could be missing necessary information that the API expects. Even if you include all the required parameters, the values you provide might be outside the allowed range or format. Try again or contact support.

Check the status of the backends to see if the chosen backend is very busy. If so, you could try submitting your job at a less busy time or select a different backend with a shorter queue. If your job requires a longer execution time, you can try increasing the max_execution_time parameter when submitting your job. If the size of your circuits (depth or shots) is a concern, consider splitting your job into smaller batches or reducing the circuit size to make them more manageable for the backend. You can include exception handling in your code to automatically retry submitting the job if it fails due to a timeout. When working with multiple jobs, running them in a session can give them priority and potentially reduce queue times compared to submitting individual jobs in job mode. Make sure to manage session lengths by either setting an appropriate max_time parameter for your session or keeping the session active by submitting jobs regularly within the interactive time limit. Try again or contact support.

Try increasing max_execution_time and resubmit.

Increase max execution time or contact support.

Before attempting to cancel, verify the current status of the job using job.status() to ensure it's in a cancellable state (e.g., 'QUEUED', 'RUNNING'). You can also check the job status on the IBM Quantum Platform dashboard. Try again or contact support.

Retry the cancellation request after a short delay. Before retrying, you can use job.status() to ensure the job is still in a cancellable state. Try again or contact support.

Check the region and region type provided in the request.

Check the bucket and object metadata provided in the request and ensure the object exists.

Check that an authorization policy granting ObjectWriter and/or ContentReader exists between the quantum-computing instance (source) and the cloud-object-storage bucket (target)

Ensure you have pushed your custom image to the proper container registry repository or contact Qiskit Runtime team.

Consider breaking down complex circuits into smaller, more manageable units to reduce compilation time. If the current backend is overloaded or experiencing issues, try running your job on a less busy backend or a simulator. Experiment with different transpiler levels or explore custom transpiler passes to optimize the compilation process for your specific circuits. Try again or contact support.

Try again or contact support.

Lower requested maximum execution time.

Verify the session ID is correct, and that you have the correct access permissions.

Try again or contact support.

Carefully inspect JSON body structure and syntax for any errors. Ensure that the values you're providing for each parameter are within the expected range and format. Pay close attention to data types (e.g., integers, strings, booleans). Try again or contact support.

Check the IBM Quantum Platform's documentation and terms of use to understand any geographic restrictions on access. If you are using a VPN, proxy, or firewall, try temporarily disabling it to see if it resolves the issue. Verify your network settings to ensure they are not blocking access to the necessary IBM Cloud endpoints. When initializing QiskitRuntimeService or saving your account, ensure that the region parameter (if used) matches the expected region of your IBM Quantum instance. You can set a region preference when initializing your QiskitRuntimeService instance. Try again or contact support.

Provide a valid active time.

Provide a valid session time by using the Session length information.

Use the information in the Session API guide to try again, or contact support.

Fix the session time limits by using the Session length information and try again.

Provide a valid session interactive time.

Specify the session execution mode correctly. For instructions, see the REST API documentation.

Make your program smaller. For example, reduce the number of instructions or split the job into multiple jobs to reduce the number of circuits. See this example for help. See Job limits to learn more.

Postpone job deletion until job is in a terminal state.

Verify and Regenerate Your API Token. If you're using IBM Cloud credentials, ensure you're providing the correct IBM Cloud API key. Make sure you are properly initializing your Qiskit Runtime service with your credentials. Try again or contact support.

Specify the account ID and try again.

Check the bucket and object metadata provided in the request and ensure the object exists.

Check that an authorization policy granting ObjectWriter and/or ContentReader exists between the quantum-computing instance (source) and the cloud-object-storage bucket (target)

Check the pre-signed URL and ensure that it is valid.

Check the pre-signed URL and ensure that it is valid.

Check the pre-signed URL and ensure that it is valid.

Try changing service instance CRN

Please, ensure the token is correctly formatted and of the expected type.

Check the CRN and try again.

Please check the API documentation to ensure all necessary headers are included.

Verify your permissions and ensure the operation is allowed for the role or action attributed to the subject.

Please check the API documentation to ensure all necessary headers are correctly included.

Create an instance of a different plan type or use a different execution mode.

Verify the current status of the job using job.status() or by checking the job details on the IBM Quantum Platform dashboard. Ensure that your IBM Quantum account or API token has the necessary permissions to delete jobs. Try again or contact support.

Verify that the account plan start/end times have valid values. The start time must be earlier than the end time.

Verify that the account plan TTLs have valid values.

Verify that the session TTLs have valid values.

Delete other instances on requested plan until the account is below the limit and try again.

Verify the workload ID and try again.

Verify the workload ID and try again.

Verify the workload ID and try again.

Request credits on related session instead

Please allow time for the job to reach a terminal state and try again.

Please allow time for the session to reach a terminal state and try again.

Upgrade your service plan or contact support to enable custom calibrations access.

Verify the calibration ID is correct.

Try again or contact support.

Verify the observables correctly correspond to the qubits. See Primitives examples for help.

Verify the parameters correctly correspond to the circuits. See Primitives examples for help.

Pass valid OpenQASM strings that can be imported into Qiskit. See Introduction to OpenQASM for information on OpenQASM and how to import it into Qiskit.

Use a resilience level supported by the Qiskit Runtime primitives. See the Available options table for details.

Use a supported version of the primitive. See the Qiskit Runtime release notes for information about what is supported.

Use the correct options for the primitive being used. See the Specify options documentation for information.

For information about the correct primitive input, see Get started with primitives.

Verify the input circuits and the transpilation options. See the Transpilation documentation for help.

Transpile your circuits for the target before submitting a primitive query. Refer to Primitives examples for code examples.

Ensure the options are specified correctly and retry. To learn more, see the Specify options documentation.

If your job contains dynamic circuits, or if the PEC, PEA, or gate twirling option is selected, then make sure to remove all fractional gates from the circuits. If you are using qiskit-ibm-runtime version 0.24.0 or higher, you can use the new use_fractional_gates keyword when retrieving a backend instance. When set to False, this returns a backend that does not have fractional gates in its target and therefore ensures the transpiler would not unroll any gates to fractional gates.

Split the circuits or PUBs into multiple jobs. See Run jobs in a batch for an example.

See Options compatibility for features that are incompatible with each other.

V2 Estimator does not support dynamic circuits. Remove control flow operations or convert the job to use V2 Sampler instead.

See Migrate from Qiskit Pulse to fractional gates for instructions on how to migrate to fractional gates.

A transient issue might have caused the ZNE failure. Try resubmitting the job to see if it succeeds. If you are explicitly configuring ZNE options (e.g., noise factors, extrapolator, amplifier), verify that they are valid and appropriate for your circuit and backend. Ensure that the noise factors are correctly specified. Confirm that a valid noise amplifier is selected. Verify that a valid extrapolator is chosen. If your circuit is very deep or complex, consider breaking it down into smaller sub-circuits or reducing its complexity to improve the effectiveness of ZNE. Monitor the status of the chosen backend on the IBM Quantum Platform dashboard to check for any ongoing issues or maintenance that might be affecting ZNE. Explore alternative implementations of ZNE. Try again or contact support.

Pass a correct list of noise factors.

Pass a valid ZNE noise amplifier.

Pass a valid ZNE extrapolator.

If you are explicitly configuring PEC options (e.g., setting max_overhead), consider adjusting these parameters. If your circuits are very complex, try simplifying them by reducing the depth or the number of operations. Explore other error mitigation techniques like Zero Noise Extrapolation (ZNE) if PEC consistently fails. ZNE might be more suitable for certain circuits or noise levels. Verify the status of the chosen backend on the IBM Quantum Platform dashboard for any ongoing issues or maintenance that might be impacting PEC. Try again or contact support.

Pass a coupling map in the correct format.

Try again or contact support.

Reparametrize your circuit in terms of ISA parametric gates, or bind it locally.

The most crucial step is to ensure that your local Qiskit environment and the Qiskit Runtime environment are using compatible versions. If your circuit is highly complex or uses many parameters, try simplifying it to see if the deserialization error is related to a specific part of the circuit. Try again or contact support.

You might have manually specified a delay duration that is not an exact multiple of the backend's dt. Sometimes, the transpiler might not perfectly align delay instructions to be multiples of dt, especially in complex scenarios or with specific transpiler passes. If you're trying to export a circuit containing delays using the OpenQASM 2 exporter, it might struggle to represent the timing information, leading to this error. Try again or contact support.

Before setting rep_delay, query the backend to determine the acceptable range. When specifying rep_delay in your options.execution for a primitive job, make sure the value you provide falls within the range returned by backend.rep_delay_range. Use backend.default_rep_delay as a starting point. Verify your settings or contact support.

Carefully review your QASM code for any syntax errors or inconsistencies. Ensure that gate arguments, registers, and other elements are correctly defined according to the OpenQASM 2 or OpenQASM 3 specification. Check for any known version compatibility problems between the version of OpenQASM you're using and the version of Qiskit running on the platform. Verify the input circuit or contact support.

Try again or contact Q-Ctrl support.

Try again or contact Q-Ctrl support.

Try again or contact support.

Fetch the job error logs to get more specific information about why the job failed. Try again or contact support.

Increase the timeout. Before submitting, verify the status and queue length of the chosen backend on the IBM Quantum Platform dashboard. If your circuits are very deep or you're requesting a very high number of shots consider reducing the complexity or splitting the job into smaller batches. Implement retry logic with exception handling. Use sessions for iterative workflows. Try again or contact support.

Remove the unexpected program input parameter and retry. For more information, see Primitive inputs and outputs.

Query the backend's configuration and properties to understand its capabilities. Ensure you're using the correct backend object and that your request parameters align with the backend's capabilities.

Use another backend to book a time slot.

Use another backend.

Check the URL being used for the upload. Ensure it adheres to the correct format for IBM Cloud Object Storage endpoints. Try again or contact support.

Select another date to book.

Review booking API documentation, verify date and time formats, check backend ID, and confirm permissions.

Check the booking to cancel.

Use another provider to book or contact your Group Administrator.

Select another date to book.

Verify the booking ID, check booking status, and check permissions.

Select another date to book.

Check the source file and feature table for supported OpenQASM 3 features.

Check the code data, maybe it is wrong.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Check your request to the endpoint.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Try to log in again.

You don't have authority to perform the action.

You don't have authority to perform the action.

You don't have authority to perform the action.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Try to use another backend.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Try to use another backend. Contact an IBM Quantum administrator.

Try to use another backend.

Try to use another backend.

Try to use another backend.

Try to use another backend.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Change the priority Value.

Use another backend.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Use another Group.

Use another Hub.

Use another provider.

Use another mode to book a backend.

Use another project.

Use another hub.

Try to use another backend.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Access another job.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Check if the action makes sense.

Check the Job sent, maybe it is wrong.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Check the Job sent, maybe it is wrong.

Change the limit sent into the request.

Change the body sent into the request. Maybe its format is wrong.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Check the job sent. Maybe it is empty.

Try to use another backend.

Try to use another backend.

Reduce the content of the job.

Check the job ID to query. It is wrong.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Check the status of the job.

Update the share level.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Try to use another backend.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Accept the license.

Regenerate the API Token.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Check your old password. It is wrong.

Check the password. It is wrong.

Try to log in again.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Accept the license.

Login using IBM ID.

Try to login again.

Accept the License.

Wait until some previous jobs were finished. You can cancel pending jobs to run new jobs.

Wait 5 minutes, then log in again.

Contact an IBM Quantum Administrator.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Check the body of the request.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Ensure your query is correct.

Ensure your query is correct.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Retry the action. If it happens again, contact IBM Quantum via Slack for help.

Try to use another project.

Do not change the session to no longer accept jobs before all jobs are created.

Do not close the session before all jobs in it are completed

None. The instance no longer exists and the remaining jobs were canceled.

If the session has been closed due to instance limit, contact your instance administrator to increase the limit or reduce the time between submitting subsequent jobs in a session.

Try again or contact support.

Try again or contact support.

Try again or contact support.

Try again or contact support.

Try again or contact support.

Try again or contact support.

Verify the job ID is correct, and that you have the correct access permissions.

Try again or contact support.

You have exceeded your monthly quota. Learn more about your current plan and explore upgrade options at the IBM Quantum Platform Products and services page.

Verify the session ID is correct, and that you have the correct access permissions.

Programs are no longer supported. Contact support for more information.

Contact support for more information.

Use a simulator backend.

Reduce the number of qubits used in the circuit to fit the device.

Reduce the complexity of the job, or number of shots.

None. Job was canceled.

Try to run the job again.

Reduce the number of shots (fewer than 10K) and stitch the results together.

Reduce the requested number of shots. See the Specify options guide for help.

Increase the requested number of shots. See the Specify options guide for help.

Reduce the number of experiments. You can try breaking your job into multiple jobs using batch mode.

Submit an OpenQASM 3 program to be compiled via backend.compile().

See specific error message for solution. Contact support if required.

Contact support or try again.

Contact support or try again.

Contact support or try again.

Contact support or try again.

Contact support or try again.

Contact support or try again.

Contact support or try again.

Contact support or try again.

Contact support or try again.

Contact support or try again.

Contact support or try again.

Contact support or try again.

Contact support or try again.

Contact support or try again.

Contact support or try again.

Contact support or try again.

Contact support or try again.

If possible, consider breaking the job up into multiple separate jobs or reducing the use of measurement results in subsequent conditions. Contact support if required.

Reduce the size of your job. This might include reducing the circuit depth, number of circuits, amount of waveform memory consumed, or the amount of control flow in your program. Review the Classical feedforward and control flow guide for help. See Job limits to learn more.

Check the device's coupling map and basis gates for supported operations

The input source is not supported by the backend. Remove the functionality reported in the error message. See the OpenQASM 3 feature table for supported operations.

A circuit could exceed the system limits. Submit a smaller program or contact support.

Instruction not supported by backend. Remove the instruction shown in the error message. Alternatively, convert the input to conform to the backend's Instruction Set Architecture (ISA). See Hello World for an example.

Remove the instruction shown in the error message. Alternatively, convert the input to conform to the backend's Instruction Set Architecture (ISA). See Hello World for an example.

Define as many classical bits as the number of qubits. See the Measure qubits guide for more information.

Remove multiple measurements on qubits. See Measure qubits for more information.

Verify that the instructions are correct.

Cannot perform any instruction on a measured qubit. Remove all instructions following a measurement. See the Measure qubits guide for more information.

Assign qubits to a classical memory slot. See the Measure qubits guide for more information.

Reduce number of samples below specified limit.

Must use available drive channels. There should be one DriveChannel for each qubit and one MeasureChannel for each qubit. Use backend.control_channel to enumerate the ControlChannel.

This instruction is not supported. Make sure that the gate name is correct. Review the Circuit Library for allowed gates.

This instruction is not understood. See the documentation about basis gates and native gates.

Check the topology diagram for this QPU (go to the Compute resources page and click the QPU) and make sure the qubits are connected.

The given measurement level is not supported on this backend. Change it to 0-2 except the measurement level specified.

Pulse experiment is not supported on this backend. Use a backend that supports pulse to run this experiment.

Conditionals are not supported on this backend. Remove the conditional instruction in your program.

Reset instructions are not supported at this time for this backend. Remove the reset instruction.

Add more samples or contact support for further help.

Due to hardware limitations, pulses must be a multiple of a given number of samples. Change the total number of samples in the pulse instructions to be a multiple of the value returned, or contact support for further help.

Reduce the number of unique waveforms and/or their length. During pulse sweeps, such as in waveform calibrations, utilize parametric pulses with varying amplitudes to efficiently reuse waveform memory. Less memory is available for measurement channels. Contact support for further help.

Reduce the total length of pulse sequence on the specified channel. Contact support for further help.

Circuit too long; reduce length of circuit. Contact support for further help.

Set acquire operations to have the same length. Contact support for further help.

Reduce the number of samples in the specified pulse. Contact support for further help.

Make the entry a positive integer.

Use only one acquire command per channel.

Fix the qubits specified in the acquire command.

Channel does not exist on system. Contact support for further help.

Repetition time must be changed to a supported value. Contact support for further help.

The delay is not supported. Contact support for further help.

Reduce the length of the job. Contact support for further help.

Add type to qobj['config'].

Two instructions cannot be played at the same time on a channel. Contact support for further help.

Due to hardware limitations, measure and acquire instructions must occur at 16 sample multiples. Contact support for further help.

Try increasing the rep_delay value or reducing the number of measurements/resets within your circuits.

Try lowering the amplitude of your input pulses. Contact support for further help.

Check your classical register sizes.

Lower the amplitudes of the input pulses. Contact support for further help.

Verify the pulse input parameters. Contact support for further help.

Ensure the pulse duration parameter is valid. Contact support for further help.

Verify that the duration of all pulses meets or exceeds the minimum pulse duration. If necessary and possible, consider zero-padding the start/end of very short pulses such that they meet or exceed the minimum duration. Contact support for further help.

Reduce the number of shots or measurements, or increase the rep_delay.

Increase the lengths of any short pulses, insert more delay between them, or both. For instructions, see Build pulse schedules or contact support for further help.

Reduce the amplitudes of any large or overlapping pulses, compensating by making them longer if needed. Contact support for further help.

Reduce the length of the program data being loaded by breaking your job into multiple jobs.

Retry and contact support if you get this message again.

Retry and contact support if you get this message again.

Make your program smaller. For example, reduce the number of instructions or split the job into multiple jobs to reduce the number of circuits. See this example for help. See Job limits to learn more.

Ensure the intended classical register is correct and available.

Ensure the classical register exists.

Try again or contact support.

Try again or contact support.

Try again or contact support.

Try again or contact support.

Try again or contact support.

Try again or contact support.

Try again or contact support.

Try again or contact support.

Try again or contact support.

Try again or contact support.

Try again or contact support.

Contact IBM Quantum via Slack for help.