Qiskit / Qiskit/documentation

Better define rolling window

Open
#5,292 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/instances#open-plan-instance, but check with ripgrep search for 'rolling' if there are other places too

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

A user in Slack was confused thinking that there was a bug with their usage:

I wanted to flag a platform bug I'm experiencing with the IBM Quantum Open Plan.
The QPU quota cycle end date May 25, 2026 – Jun 22, 2026 (UTC) keeps incrementing daily instead of remaining fixed, so the cycle never completes and quota never replenishes.

I explained this is intentional:

Hi, so IBM uses what is called a rolling window. It is intentional that every day, the 28 day range shifts forward by one. The quota is based on your last 28 days of usage.

So, imagine that 28 days ago, you used 5 minutes and 27 days ago you used the remaining 5 minutes. Today, we'll say you have 0 minutes left. But tomorrow, the 28-day-usage will become 29 days and no longer be considered. The 27-day will become 28-days. So, tomorrow you'd have 5 minutes total. Then in two days, you'd have 10 minutes total

We should make our docs more clear. Given that multiple plans use a rolling-window, maybe have one common place where we define rolling window, then refer to it everywhere.

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

I can help the team by providing enough information or by referring them to a specific Subject Matter Expert to write the material

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 Open Plan guide at https://quantum.cloud.ibm.com/docs/en/guides/instances#open-plan-instance, then use ripgrep to find other mentions of “rolling.” Identify the shared documentation location and the plan-specific references that need updating. Done means users can understand that the 28-day quota is based on recent usage and shifts forward daily, with consistent wording across relevant plans.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.