Major Description
If you have a workflow with a fork and restart the JobTracker while its executing the paths in the fork, those two jobs will be lost (as expected). Once the timeout occurs on the ActionCheckXCommand, it will check both actions sequentially. While checking the first action, it sets the status to FAILED and also sets the workflow's status to FAILED. It then moves on to the other action that was running concurrently, but it cannot pass the precondition check because the workflow was already FAILED (the check requires that the Workflow is RUNNING). It will keep trying this every time the timeout hits (10min is default) and print a WARN message in the log. That action will also be in RUNNING state forever even though the underlying job isn't running and the WF is FAILED.