onAutoScheduleNoConverge

info

This functionality is available in the PRO edition only.

Description

Fires when auto scheduling cannot settle on a stable result

onAutoScheduleNoConverge: (result: object) => void;

Parameters

• result - (required) object - details of the scheduling run, including the number of iterations performed and the list of conflicts collected.

Example

gantt.attachEvent("onAutoScheduleNoConverge", function(result){
    console.warn("Auto scheduling did not converge", result.conflicts);
});

Related samples

• Auto Scheduling extension

Details

note

This event is defined in the auto_scheduling extension, so you need to activate the auto_scheduling plugin. Read the details in the Auto Scheduling article.

Auto scheduling places tasks in repeated passes until the result stops changing. This event fires when the result keeps changing and the engine stops after a number of passes without reaching a stable state. In practice this points to an over-constrained project - for example, a set of constraints and dependencies that cannot all be satisfied at the same time.

The result parameter contains the details of the run:

• iterations - number - how many passes were performed.
• converged - boolean - false in this event.
• conflicts - array - the conflicts collected during scheduling (see onAutoScheduleConflict for the conflict fields).

Related API

• auto_scheduling
• auto_scheduling_move_projects
• auto_scheduling_use_progress
• findCycles
• isCircularLink
• onAfterAutoSchedule
• onAfterTaskAutoSchedule
• onBeforeAutoSchedule
• onBeforeTaskAutoSchedule
• onAutoScheduleCircularLink
• onAutoScheduleConflict

Related Guides

• Auto Scheduling

Change log

• added in version 10.0