Some messages come only from forecasts, calibration, portfolios, scenarios, AI investigation or a very large board. This page lists them by cause, with what to do. The other messages are on Troubleshooting & FAQ.

Forecasts and calibration #

• “The data does not support this forecast”: there is not enough observed delivery history. Select Review the forecast inputs.
• “This board has more work items to deliver than one forecast covers”: forecast selected work items, or a number you supply, instead (Run a forecast).
• “Nothing in this run can be forecast now”: none of the work items this run selected can be forecast on this board now. Forecast other work items, or a number you supply, instead (Run a forecast).
• “This board is too large to calibrate in one evaluation”: narrow what the board holds, or calibrate a schedule’s captured forecasts on “When will this scope finish?”.
• “Calibration is not possible yet on this board”: a past date is replayed only over work the board was seen to hold then. Once the board’s Data as of reaches the day the message names, create a new backtest with the same number of origins and days between them. Where it names no day, it says what the board still needs: open work items observed, or delivered work items in the days behind its origins (Forecast calibration).

Portfolios and scenarios #

• “These boards measure different things”: their flow definitions differ, so a total would mean nothing. Select Compare the definitions.
• “The dependencies form a cycle”: two or more items depend on each other. Select Open the dependency inspector.
• “Choose who does the shared work”: some work items belong to scopes with the same rank on different streams. Name the executing stream for each of them, or change a rank, then run again.
• “Choose which board counts shared deliveries”: two boards of the run delivered the same work items. Choose which board counts them, then run again.
• “You can’t change or run this scenario”: some of its parts name boards or work items you cannot open. Ask for access to them.
• “This plan proposes more changes than one check covers”: narrow the plan (fewer dated scopes, dependencies or WIP changes) and check again (Scenario results and the apply plan).
• “This read spans more work than one authorized read can check”: a manager of the portfolio narrows the portfolio or the value stream.
• “This scenario waits on too much work outside it”: its work waits on more than 1,000 work items outside the scenario, so the run stops. Nothing is missing from the boards’ data. Remove some links, or add that work to the scenario.
• “A work item scope reads at most … work items on one level under it”, with the limit in place of the dots: set the scope on a work item lower down, or as a list of work items.
• “Jira did not finish answering”: Jira stopped before it said which work outside the scenario is not done, so nothing was written. Run the scenario again; this usually passes on its own.

Large boards and board settings #

• “This board is too large to rank in one request”: select Rank the whole board in the background.
• “This board is too large to take its dates back out of Jira in one step”: narrow what the board holds, or leave the dates where they are. Dates moving from the app into Jira have no such limit.
• “The hierarchy shows at most … work items on one level”, “A rollup reads Jira fields for at most … work items at once” or “The hierarchy is followed at most … levels down”, each with the limit in place of the dots: a Board owner narrows the board’s source, for example to fewer parents or fewer levels.
• “This Jira board keeps no sprints”: sprints belong to a Scrum board. Choose another Jira board.
• “This rule cannot be accepted yet”: a class of service on the board names a saved filter, or a query Jira cannot read. A Board owner changes the class’s query.

AI investigation #

• “AI investigations are busy”: your question waits and continues by itself.
• “The model is unavailable”: what the investigation gathered is kept. Select Try again.
• “AI is paused” or “The budget for this period is used up”: no AI question runs until the time the message names. An administrator reviews the spending (AI investigation settings).
• “AI investigation is off”: an administrator has not turned it on, so ask one to turn it on (AI investigation settings).
• “AI is not set up yet” or “AI investigation is not set up for this site yet”: the vendor completes the setup, and there is nothing to do on your side.
• “The cap is below the most one call can cost”: an administrator raises the cap, never above the vendor allowance.
• “A call cost more than expected”: no question runs until the daily budget resets at the time the message names. Raising the cap does not change it.
• “Other questions are running”: they hold the budget for now, so select Try again once they finish.
• “You have reached the number of investigations one person may keep”: delete an investigation you no longer need, or wait for the oldest to expire on the date the message names.

Still stuck? #

Select Get Help in the app’s navigation. It opens the vendor’s support portal. An administrator can attach a support bundle to the request (Support and diagnostics).