[Canonical page](<https://docs.dhtmlx.com/planning-engine/java/api/results/overview/>)
[Full documentation index](<https://docs.dhtmlx.com/planning-engine/llms.txt>)


# results

The output of a scheduling call. [`ScheduleResult`](<https://docs.dhtmlx.com/planning-engine/java/api/results/schedule-result.md>) is what [`Project#solve`](<https://docs.dhtmlx.com/planning-engine/java/api/project-solve.md>), [`Project#preview`](<https://docs.dhtmlx.com/planning-engine/java/api/project-preview.md>), [`Project#analyze`](<https://docs.dhtmlx.com/planning-engine/java/api/project-analyze.md>) and [`Engine.schedule`](<https://docs.dhtmlx.com/planning-engine/java/api/engine-schedule.md>) return. It holds the baseline token, the changed tasks as [`Mutation`](<https://docs.dhtmlx.com/planning-engine/java/api/results/mutation.md>) records, dependency cycles, [`Conflict`](<https://docs.dhtmlx.com/planning-engine/java/api/results/conflict.md>) and [`Note`](<https://docs.dhtmlx.com/planning-engine/java/api/results/note.md>) entries, the convergence flag and, when requested, [`Analytics`](<https://docs.dhtmlx.com/planning-engine/java/api/results/analytics.md>). Conflicts and cycles are reported as data in the result, not thrown. The overallocation and load profile fields use types from [resources](<https://docs.dhtmlx.com/planning-engine/java/api/resources/overview.md>).

[`Reason`](<https://docs.dhtmlx.com/planning-engine/java/api/results/reason.md>), `Conflict` and `Note` are abstract classes with a closed set of nested subclasses (`Reason.Asap`, `Conflict.ConstraintViolation`, `Note.DroppedTask`, ...). Match them with `instanceof` or `switch` patterns. Every type here is in the `org.dhtmlx.plen` package.

:::category-index
:::