Notifications and warnings

Notifications and warnings

The app tells you what is going on in four places: the status bar at the bottom, the Warnings panel in the right-hand column, the notifications that appear briefly at the bottom of the screen and the strips under the ribbon. This article says for each place what you see, when it appears and what you can do about it. Why a schedule is critical or overallocated is in Critical path and float; resolving overallocation is in Resolving overallocation; making relations is in Adding relations.

The difference between the four

• Status bar — a fixed line with counters. They come from the last calculation and stay until you calculate again.
• Warnings panel — the list behind those counters, with everything the last calculation found, and a click takes you to the task, relation or resource. It is derived from the last calculation; nothing is stored.
• Notifications — short messages about something you just did (saving failed, relation refused, import read). An info disappears again, an error stays until you close it. They are not in the panel.
• Strip under the ribbon — a coloured strip with an explanation and one button. It belongs to a state of the document or of a mode and stays as long as that state applies. See The strips under the ribbon.

The status bar

The bar at the bottom shows, from left to right:

• Tasks: — the number of leaf tasks (summary tasks do not count).
• Milestones: — the number of milestones.
• Critical path: N tasks, N work days — the number of critical tasks and the project duration. Only visible after a calculation.
• End: — the project finish from the calculation. Only visible after a calculation; an empty project has none.
• N deadline(s) missed, N constraint(s) violated, N out-of-sequence relation(s) and N resource(s) overallocated — each a button with a warning sign, only visible when the counter is above 0 and there is a calculation. A click opens the Warnings panel (tooltip: Open the Warnings panel (details and navigation)). If you are on the IFC or Report tab, the app jumps to Home at the same time, because the right-hand column does not exist there. The resource(s) overallocated counter also refreshes after changes to resources and assignments; the other counters only change after Calculate. The four counters are a selection: what the panel shows in addition (truncated lead, ignored relation, hammock without a finish driver, capped finish date, schedule error) is not in the status bar.
• Out of date — recalculate (F5) — with a warning sign (tooltip: Schedule out of date — recalculate (F5)). Visible as soon as you change something that affects the schedule and have not recalculated. If Calculate automatically is on it stays away, except when the calculation gave an error: then it stays.
• Selection: N task(s) — the number of selected tasks; only visible with a selection.
• Scale: and Zoom: Npx/day — the time scale of the timeline and the zoom level. The scale follows from the zoom.
• Unsaved — as long as the document has changes that are not in the file.
• AI — a coloured dot with the word AI, only when AI mode is on. The tooltip says AI bridge: with Off, Live on port N, Port N in use or Error. A click opens the AI tab.
• Debug terminal — a terminal button, only when the debug terminal is enabled; it shows or hides the terminal (Show debug terminal / Hide debug terminal).

The Warnings panel

• Opening — Planning › Schedule › Warnings, View › Panels › Warnings, or a counter in the status bar. The panel is in the right-hand column, below Properties and the resource dock, and expands a collapsed column. By default it is closed and it is not remembered between sessions. You drag its height at the edge when it is under other panels, and that height is remembered. The cross at the top right closes it (Close warnings).
• Header line — N error(s), N warning(s). If nothing has been calculated yet, it says Not calculated yet — press Calculate (F5) to run the checks.
• Calculate — a button in the header line, visible as long as the schedule is out of date or not yet calculated. It does the same as Calculate in the ribbon.
• Warning sign in the header line — when the schedule is out of date, with the tooltip Schedule is stale — this list comes from the last calculation. Recalculate (F5). The list is not hidden, only marked as out of date.
• Empty list — No warnings. The schedule passes all checks.
• A line — at the top the place (task, relation, resource or project) and under it the description. An error has its own octagonal sign, a warning a triangular sign. A task appears as WBS name. A relation appears as predecessor → successor (FS+2d), with type and lag. A click goes to the place (tooltip Go to: …), see below. The line that belongs to your active task (for a relation: its successor) or to the resource chosen in the histogram is highlighted.
• Order — errors first; then per kind in the order of the list below; within a kind in document order (for a relation that of the successor, for a resource that of the resource list). A task, relation or resource that was deleted after the last calculation drops out.

Kinds of warning

• Schedule error — The schedule could not be calculated: … with the reason after it, see below. A click: for a cycle the app selects all tasks in the cycle and jumps to the first; for other errors there is nothing to jump to and the line is not a button.
• Deadline missed — Deadline {date} missed — early finish {date}. The task has a deadline and the calculation does not meet it. A click jumps to the task. To fix: adjust the logic or the duration, or move the deadline.
• Constraint violated — Constraint {type and date} is overridden by the logic (negative float). The constraint cannot be met without breaking the logic; the float is negative. A click jumps to the task. See Constraints.
• Out of sequence — Out of sequence: the successor's progress contradicts the relation. The progress of the successor does not fit the type of relation, for example a successor that is already in progress while the predecessor is not yet done under a Finish-to-Start relation. A click selects both tasks, with the successor active. Check the actual dates or the relation.
• Lead truncated — Lead truncated by the project start — the relation is not fully honoured. The lead (negative lag) of the relation reaches before the project start. A click selects both tasks.
• Relation ignored — Relation ignored: predecessor or successor is missing or is not a leaf task. The calculation does not use the relation. A click selects the tasks that still exist. See Relations.
• Hammock without a finish driver — Hammock without a finish driver (no FF/SF predecessor): its duration falls back to zero. A click jumps to the task. See Hammock tasks.
• Finish date capped — Finish date capped: the calendar leaves no workable window for this task. The calculation hit the limit of the number of days it searches, for example because of a very long unbroken stretch of days off in the calendar. A click jumps to the task. See Calendars and working days.
• Overallocation — Overallocated on N day(s) (first – last), with the resource does not work these day(s) per its calendar added if all days are days off, or of which N day(s) the resource does not work per its calendar for a mix. A click selects the tasks with an assignment on that resource, turns the histogram on and chooses that resource in it; from Table, IFC or Report the app jumps to Resources. See Resource panel.

Reasons for a schedule error

• Circular dependency between tasks: {path} — the relations form a cycle. The tasks are in the path; reverse or remove one relation.
• The calendar has no working days set — give the calendar at least one working day, see Calendar windows.
• Invalid duration in days for task '{task}' and Invalid duration in hours for task '{task}' — the duration of the task is not a valid number.
• Hour task '{task}' has no valid working hours in its calendar — a task in hours on a calendar without working hours.
• Invalid start date for task '{task}' — the start date of the task is not valid.

The strips under the ribbon

A strip sits directly under the ribbon, above the workspace. It has a text and one button. A strip for a mode has no cross; you close the others with the cross. The five strips:

• Link mode — Link mode: drag from one bar to another in the Gantt to create a relation. Press Esc to stop. It stays as long as link mode is on. Button: Stop. See Adding relations.
• Split mode — Click a bar on the day the break starts and drag right for its length. Press Esc to stop. It stays as long as Split task is on. Button: Stop.
• Hour planning in the file — This file contains hour-based planning. It appears when an opened file contains hour planning while Enable hour planning is off. Button: Enable hour planning. See Turning on hour planning.
• Structure locked — Not available while filtering/grouping/sorting. It appears when indenting or outdenting is refused because the task list is filtered, grouped or sorted. Button: Clear, which removes the filter, grouping and sorting.
• Dates as recorded — after opening a file where recalculating moved dates: Recalculation moved N of M tasks away from the dates in the file. with the button Show recorded dates. While the view is on: You're viewing the dates as recorded in the file … with the button Recalculate. See Dates as recorded.

Notifications

Notifications appear at the bottom of the screen, also in the table, in Backstage and in presentation mode. A notification is an error or info. An error is red and stays until you click the cross; an info disappears after 5 seconds (a notification with a lot of explanation stays longer), and those timers start again as soon as the stack changes. Each notification has a cross at the top right (tooltip Close notification) that closes it at once. A click on the text of the notification does nothing. A refusal is always an error: a notification that the app did not carry out something you did, such as a refused relation, duration, start or milestone. So you do not miss it if you look away for a moment. A refusal does disappear after Ctrl+Z or Ctrl+Y and when you go to another document, because it is then no longer correct. Another error, such as Failed to save, stays. That also applies if the rest of the same action did succeed, for example when pasting into several cells. If several tasks are involved, a line below says which tasks were not changed, for example Not changed: Foundation, Masonry. With more than five, it ends with and N more tasks. The same refusal folds into one line with a counter when it repeats. At most three are shown at once. If a fourth comes, the oldest info goes first. If there is no info, the oldest refusal goes, then the oldest sticky opening notification, and only then the oldest error. So an info or a refusal never pushes out another error, such as Failed to save. The stack moves away from the buttons of an open dialog and from sticky action bars. A notification when opening a file also stays until you click the cross if the app filled in, replaced, repaired or left out data while opening: a line about parser or calendar findings, number format problems, enum fallbacks, P6 scheduling settings with a safe fallback, a protective baseline fallback, ignored baseline references, activities without a planned start that were given a start, relationships between projects or activities without a project that were not imported (P6 XML), something from an MS Project file that was not imported (MS Project XML and .mpp) or an unusable XER source archive, and the notifications about duplicate ids and relations that are not calculated. If it only contains information without such a change (such as the number of projects, documents or the text encoding), the notification disappears after 5 seconds.

• Counter ×N — a notification with a fixed key folds a repeat into one line with a counter, for example a save error that keeps coming back or a refused relation that you repeat. Not every notification does that.
• Read more — some notifications have a Read more link or a topic of their own (for example Task types explained) to the guide in Backstage › Help.
• Action button — the notification about the calculation profile has a button Open calculation profile to Project settings.

The list below is a selection, grouped by topic. Where it does not say otherwise, it is an info.

Saving, opening and recovery

• Saving failed (error) — Failed to save with the reason below it. When saving, saving as and exporting a report.
• Saved as a download (info) — Saved as a download: '{name}' is now in your downloads folder. … With Save As and exports, when the environment does not let the app write directly to the location you picked. Two downloads right after each other fold together.
• Saved as a download (explanation) (info, 15 seconds) — Saved as a download: '{name}' is in your downloads folder. This browser does not let the app write to a place of its own, … With Save in a browser that only saves through a download. Once per session, with a link to the explanation of files.
• Browser does not write back (info, 15 seconds) — This browser does not let the app write back to '{name}'. … With Save of a project that has a file, when the browser has to ask for a place again. Once per session, with a link to the explanation of files.
• Auto-save failed (error) — Auto-save failed with the reason. Applies to auto-saving to the file and to crash recovery.
• Library could not be saved (error) — Library could not be saved, when saving the resource library.
• Opening a file failed (error) — Failed to open file with the reason. For an example, a recent file or an imported file.
• Old or protected .mpp (error) — This .mpp file uses an older format (Project 2007 or earlier)… or This .mpp file is password-protected…, both with the advice to export as XML in MS Project and open that file.
• Invalid XER file (error) — one of the XER… texts, for example This is not a valid or supported XER file. or The XER file contains a duplicate table., with the reason added.
• IFC could not be read (error) — IFC could not be read with the reason, in the IFC view.
• Recovery (error) — Recovered file could not be read, Restore failed and N recovery files could not be loaded and were skipped. When recovering after an unexpected shutdown.
• Branch saved as template (info) — Branch saved as template '{name}'.
• Message from an extension (info, or error if the extension reports an error) — Extension {name}: {message}. An extension may show at most three new ones per 10 seconds, so it does not fill the stack. If a step of an extension's guide fails, it says A step from the extension {name} failed. The guide continues., and if a project file of an extension cannot be opened, The project file {file} from the extension {name} could not be opened. Both are errors.
• A change came in between (error) — A change by the AI assistant or an extension came in between. … When you cancel the task dialog while the AI or an extension changed something in the meantime: the task edits from before that change are not reverted and remain as ordinary steps under Undo.

Calculating

• Schedule could not be calculated (error) — Schedule could not be calculated with the reason below it (see Reasons for a schedule error). On Calculate, when switching documents and when opening a file.
• Status date set to today (info) — Status date set to today ({date}). When entering progress in a project without a status date. The app measures progress up to the status date, so without a status date it cannot process progress. You set a different date under Planning › Baselines & progress › Status date. With a Read more link to Progress, status date and baseline.
• Duration shorter than the work done (error) — '{name}' is already {N}% done: a duration shorter than the work already done isn't possible. The duration was not changed.

Relations and hierarchy

• Relation refused (error) — That relation already exists, A relation between a task and its own (grand)parent summary task is not allowed. or This relation would create a cycle in the schedule ({cycle}) and was not created. The cycle names the tasks, so you know which relation to remove or reverse first.
• Move refused (error) — This move would create a cycle in the schedule ({cycle}): a summary task's relations also apply to its subtasks. Nothing was moved.
• Relations drop out after a move (info) — After the move, N relations link a task to its own summary task; they no longer count in the calculation.
• Relations skipped on insert (error) — N relations were not created: invalid link…, when pasting or inserting a branch. A line below says which relations, for example Not created: Foundation → Masonry.
• Relations not counted after import (info) — N relation(s) could not be included in the calculation. Check the Predecessors and Successors columns.
• Duplicate ids after import (info) — Objects with a duplicate id in this file: N. They were given their own id…

Editing tasks

• Start recorded as a constraint (info) — '{name}' starts no earlier than {date} (SNET). When you change the start of a task with a predecessor. The predecessor determines the start, so the app records your date as a Start no earlier than (SNET) constraint. After recalculating (F5) the task won't start before that date. If the task already had such a constraint, it says '{name}' now starts no earlier than {date} (SNET).; for several tasks at once it gives a count. With a Read more link to Constraints and deadlines.
• Start not applied (error) — The new start of '{name}' was not applied: the task has a predecessor and the constraint {type} {date}, and those determine its start. Change that constraint to move the start.
• Milestone refused (error) — '{task}' has resource assignments and cannot become a milestone. Remove the assignments first. or '{task}' is a summary task with subtasks and cannot become a milestone. When converting in the task dialog, the properties panel, the context menu and the table.
• Assignments moved to a subtask (info) — Assignment moved to subtask '{child}'. or N assignments moved to subtask '{child}'. When an extension gives subtasks to a task with assignments. That task becomes a summary task, and a summary task carries no assignments itself. That is why they move to the first new subtask. In the app itself you choose this in the window Task becomes a summary task; this message does not follow. With a Read more link to Adjusting the structure.
• Milestone flag removed (info) — '{phase}' is no longer a milestone. When a milestone gets subtasks. A milestone is a moment without subtasks; with subtasks it becomes a summary task. With a Read more link to Adjusting the structure.
• Question out of date (error) — The tasks or assignments changed while the question was open. Nothing was changed; please try again. When you choose in the window Task becomes a summary task, but the question no longer matches.
• Summary task refused (error) — '{phase}' cannot become a summary task: … with the reason, and Nothing was changed. When an extension gives subtasks to a task with assignments and the assignments cannot go to the first new subtask. In the app itself this message does not appear: there the window Task becomes a summary task asks what to do, and Move is then disabled.
• Cells skipped on paste (error) — Skipped N cells: they are read-only (for example an auto-numbered WBS code or a calculated column).
• References cleared on paste (info) — N references did not exist in this document and were cleared (task calendars, custom work categories, activity codes or custom fields from the source document).
• Structure is locked (error, red strip below the ribbon) — Not available while filtering/grouping/sorting, with the Clear button. While the list is filtered, grouped or sorted: when indenting, outdenting and dragging, with Insert above and Insert below (right-click menu or shortcut). The strip stays until you click the cross, use Ctrl+Z or Ctrl+Y, or go to another document. See Adjusting the structure.
• Task added at the end (error) — The new task was added at the end. While filtering, grouping or sorting, the app cannot place it below your selection. With the Clear button. With Task and Milestone ▾ while a task is selected and the list is filtered, grouped or sorted. The task is added, but at the bottom. Clear removes filter, grouping and sorting and closes the notification. See Adding tasks and milestones.
• Task type adjusted durations (info) — After the calendar change the task type adjusted the duration of N tasks (work stays, hours per day changed). With a link Task types explained.

Primavera P6 XML

• P6 XML file opened (info) — P6 XML file opened: N project documents. After opening a P6 XML file.
• Not imported (stays) — N relationships between projects were not imported as relationships. and N activities without a project were not read. Check whether your schedule is complete.
• Empty or unusable (error) — nothing opens. Three reasons: This file contains no activities the app can read., The activities have no ObjectId. … and The file uses XER column names … Open the .xer file itself.

Primavera (XER)

• XER file opened (info) — XER file opened: N project documents. One notification per file, even if the file opens several projects, with a Read more link and detail lines below it. Always N projects found. Only when the number is above 0: N empty projects skipped., N baseline projects excluded., N baselines materialized., N dangling baseline references ignored., A protective baseline fallback was used. and N external links preserved. Only for an encoding other than UTF-8: Text encoding selected: {encoding}. Further, when the number is above 0: N parser findings., N calendar findings., N number-format findings., N enum fallbacks. and N P6 scheduling settings used safe fallbacks.
• Dates as Primavera recorded them (detail line in the same notification) — N tasks show the dates as Primavera recorded them (not recalculated). N counts every task for which the file recorded dates, including the ones that do not differ. Or, if the mode did not turn on, N tasks differ from the dates in the file — you can show them.
• XER source archive unusable (info) — The XER source archive in this file is unusable and was left out; the project itself opened in full. with the reason (for example Reason: the checksum does not match the source bytes — the archive is damaged.) and the consequence (The schedule, the calculation profile and all project data from the IFC are complete. …). When opening an IFC file in which a previously stored XER source archive cannot be used. Also when restoring after an unexpected shutdown, if the recovery storage no longer holds the source archive.
• Export loses XER information (info) — Exporting to {format} loses XER source information. After a successful export to a format other than IFC of a project with data that only exists in an XER file. With a Read more link.

Importing, exporting and calculation profile

• Dates as in the file (info) — N tasks show the dates as recorded in the file (not recalculated). (N counts every task with recorded dates) or N tasks differ from the dates in the file — you can show them. When opening a file with recorded dates.
• Work and task types visible (info) — This file contains stored work or task types; the task type and remaining work are shown for this project.
• MS Project schedule read (info) — This MS Project file contains N tasks with a split, leveled, or resource-driven schedule. They are imported and shown as such.
• Breaks not exported (info) — N tasks with breaks were exported without their breaks: MS Project/P6 only know breaks as a work distribution. When exporting to MS Project or Primavera.
• Project start moved (info) — N tasks moved with the project start. When you set the project start later. Only tasks without a predecessor and without a constraint that would lie before the new start date move to that date. With a Read more link to New project and Project settings.
• Date window no longer steers (info) — MS Project's date window no longer drives N tasks after this edit; … Once per document.
• Leveling delay rounded (info) — Leveling rounds MS Project's minute-precise leveling delay for N tasks to whole workdays. Once per document.
• Calculation profile applied (info) — This project calculates as {profile}. Change it via File → Project settings → Calculation profile and options. With the button Open calculation profile. After applying a profile, After applying, N tasks moved. follows if needed.