ecFlow's documentation is now on readthedocs!

In ecflow 4 series, the GUI exposes the why command. This is used to determine why a task has not run.

This uses the last synchronised definition on the client-side.

However, if the GUI has not been synced with the server for a while, the definition on the client-side will have an out of date suite clock.

Hence the reporting of suite time for time attributes in the Why tab can be misleading.

This situation has been improved in the 5 series. Now the Why tab will force the GUI to sync with the server before the information is shown.

Also if a node has a trigger and complete expression, the trigger is not shown, if the complete expression is true. (ecflow 5.3.2)