results#

The output model. ScheduleResult is what Project::solve, Project::preview, Project::analyze and schedule return. LevelingResult from Project::level adds a round count. The other types in this folder are its parts: Mutation entries with new dates, the Reason a task moved, Cycle, Conflict and Note diagnostics, and Analytics with the critical path and slack. Cycles and conflicts are data in the result, not errors.

• AnalyticsCritical path and slack of a schedule, present when the call's analytics options request them
• AnalyticsStatusWhether the critical path and slack in an analytics result could be computed
• ConflictA scheduling conflict reported in a result, a constraint that overrode a link or a task placed on non-working time
• CriticalThe critical tasks and links of a schedule, as ids
• CycleOne dependency cycle found in the project, as its tasks and links
• MutationOne task's new dates, duration or leveling edits in a scheduling result
• MutationKindKind of the task an update entry in a schedule result refers to
• NoteA record left out of the schedule, or a fix made to the input under repair validation
• ReasonWhy the planner placed a task where it did - a link, a summary move, a constraint or its own preferred date
• ScheduleResultResult of solve, preview, analyze and schedule - updates, cycles, conflicts, notes and optional analytics, load and profile data
• TaskSlackTotal and free slack of one task, in the configured duration unit
• ViolationWhich bound of a task's dates a constraint violation concerns - earliest or latest, start or end