A forecast schedule keeps its runs, so you can see how the forecast moved from run to run. Here you start, pause and resume schedules, and you read why one paused or waits.
Run, pause and resume #
Open a board, select Forecast, then choose Schedules. A row’s menu holds Run history, Run schedule now, Pause schedule and Resume schedule. Run active schedules above the table runs every active one.
A Board owner or the schedule’s own person can use them. Run schedule now and Run active schedules ask you to confirm with Run it now or Run them now. Pause schedule and Resume schedule act at once. The dialog says the schedule runs as the person who accepted it, and keeps a retained summary that every viewer of this board can open. Each reader is still checked against their own access. A run already queued is not started twice.
What you see after you select:
- Run: “The run is queued.”, or “A run was already queued or in progress, so this did not start a second one. That run or the next one is kept.” After Run active schedules, each schedule gets its own line, such as “Weekly release outlook: The run is queued.”
- Resume: “<name> is resumed. The run is queued.” or “<name> is resumed and waits for its next run.”
- Pause: “<name> is paused.”
- Refused or unsure: “<name> was not paused. <status>.” or “<name> may not have been paused. <status>.” (the same for resumed). Read the row again to see which state it is in.
- Nothing to run: while no active schedule is yours to run, Run active schedules is held, and its tooltip reads “No active schedule on this board is yours to run.”
Outcomes and pauses #
The State column shows “Active” or “Paused”, with an (i) for the reason and the way out. A paused schedule never resumes on its own.
The last run reads one of these:
| Outcome | What it means | What to do |
|---|---|---|
| Ran | A run started and is kept in the run history | Nothing |
| Skipped: nothing material changed | The material-change check found too little, so no run started | Nothing |
| Checked line | The same, with both times, for example “Checked Oct 20, 2026, 8:00 AM: nothing material changed since the run of Oct 13, 2026, 8:00 AM” | Nothing |
| Skipped: the board was at its run ceiling | The board already had as many runs in progress as it allows, or Jira had no room left for background work, so this pass started none | Nothing: the next run time tries again |
| Deferred to tomorrow: the day’s runs were used up | The schedule reached its limit of 24 runs a day | Nothing: it runs again the next day |
| Has not run yet | No run has happened | Wait for its first run time, or select Run schedule now |
| Resumed: waits for its next run | It was paused, then resumed, and no pass has come since | Nothing |
| No outcome recorded yet | No outcome is stored for the schedule | Nothing |
| Paused | The schedule is paused | Read the (i) in State, then the list at the end of this page |
| Waiting line | The schedule waits for a cause to end, for example “Waiting for Atlassian to confirm this site’s license” | Nothing: it runs once the cause ends (see the end of this page) |
Read the run history #
Choose Run history to open the kept runs, newest first. The card is titled “<schedule> · run history”. If the schedule is gone, it says “This schedule is no longer on this board’s list. Its retained runs stay readable under the retention period.”
| Column | What it shows |
|---|---|
| Run | When it ran and, under it, “As of” its data time and “Flow version” with its number |
| Headline | The date or count at its probability: “85%:” and a date, “85%: beyond the horizon”, or “85%: at least” and a count for a count question; else “No headline recorded” |
| Scope | The work items left, as a count of work items |
| Reason for movement | What differs from the run before (below) |
| Revision | “Revision” and its number, a link to the run while the detailed run is stored |
After its retention period, Revision is plain text, and the row reads “The detailed run passed its retention period and is no longer stored.” A run its owner deleted reads “Run deleted”. A run you can’t read whole reads “Not available with your current access”, and its (i) says why. With none kept, the history reads No runs kept yet.
Reason for movement lists the facts that differ from the run before. They are work items added or removed, first deliveries added to the window or fewer first deliveries in it, a changed flow, calendar, model or question, a moved start date, or a new draw. None is stated as a cause.
Under the sentence, one yellow lozenge stands for each data warning of that run, such as Experimental, Partial history or Calendar gap. They are the warnings a run’s page lists under “Before you share this” (Read a forecast result), so a moved date can be read beside what limits it. The warning that only names the model is left out here.
The cell reads “First run: there is nothing to compare it with” for the first run, and “Nothing measured changed” when nothing differs. It reads “Not compared” when the run before includes work items you cannot read, or is no longer stored.
For example, the run history of Weekly release outlook on Release train lists one run each Monday. If this week’s row reads “3 work items added”, the scope grew since last week. Read that beside the new finish date before you decide that the team slowed down.
If something looks off #
- “Paused: nobody has accepted running it yet.”: somebody with a direct role on the board selects Run as me.
- “Paused: the person it ran as stopped running it.”: somebody with a direct role on the board selects Run as me.
- “Paused: the person it runs as lost their role on this board.”: resume it once that role is back, or run it as yourself.
- “Paused: the person it runs as can no longer be read by Jira.”: somebody else selects Run as me, or resume it once that account is readable again.
- “Paused: this installation does not run the Advanced edition.”: resume it once this installation runs the Advanced edition.
- “Paused: this schedule’s board or settings could not serve a run.”: check the board and the schedule’s settings, then resume it.
- “Paused: this board’s last refresh failed, so its data is out of date.”: resume it once the board has refreshed.
- “Paused: the scope grew past what one run may cover.”: narrow the scope, then resume it.
- “Paused: every work item in this scope at the board’s counting level is delivered.”: choose work items at the board’s counting level still to deliver as its scope, then resume it.
- “Paused: the app cannot read Jira on anybody’s behalf until it is upgraded.”: resume it after the app has been upgraded.
- “Paused by an owner.”: a Board owner selects Resume schedule.
- “Waiting: the board was last confirmed against Jira more than 6 hours ago, and it runs once the board updates”: check the board’s last import on its Overview.
- “Waiting for a source that includes completed work”: widen the board’s source to include completed work (Source and scope).
- “Waiting: every work item in its scope at the board’s counting level is delivered, and it checks again for new work” or “Waiting: the board is being recalculated, and it runs once that ends”: nothing to do; it runs by itself.
