Qiskit / Qiskit/documentation

Allocation page should say what happens when limits aren't set

Open
#5,146 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

content 📄
Dominant language
Jupyter Notebook
Stars
106
Forks
223
Avg merge
1d 8h
Merged PRs (30d)
72

Description

URL to the relevant guide or resource

https://quantum.cloud.ibm.com/docs/en/guides/allocation-limits#what-happens-when-the-limit-is-reached

Select all that apply
  • new content request
  • typo
  • code bug
  • out-of-date content
  • broken link
  • other
Describe the fix or the content request.

This section needs to say what happens if an allocation limit is exceeded but a limit was not configured on the instance. My understanding is that the instance will drop in priority, but it can still be eventually picked up as long as the overall account still has remaining usage.

--

This sentence is also potentially misleading:

Collaborators can submit new workloads, which will remain queued until more time is available.

My naive understanding is that when a limit is set, adding more time to the overall account won't actually help at all with running the workload. What specifically would need to change is increasing the allocation for that instance, or removing the instance limit.

Maybe the rolling window resets this? Like another way to have those new workloads accepted is wait for the next 28-day window?

For new content requests - if the request is accepted, do you want to write the content?

I only want to review the material when it's finished

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the allocation-limits guide at the linked “What happens when the limit is reached” section. Verify the behavior for instances without configured limits, account usage, allocation changes, and the rolling window before revising the explanation. Done means the section accurately describes each case and the queued-workload sentence is no longer misleading; request review afterward.

Written by the indexing model from the issue text.

Assessment

Domain
cloud, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.