anchor.diff:  
   [source,javascript]
   ....
  -// A slot at time T will wait until the current time is one hour after the slot's time.
  +// A slot at time T will wait until the current time is one hour after T.
   celos.delayTrigger(60 * 60)
   ....
   
  
positive.code: 
  [source,javascript]
  ....
  // A slot at time T will wait until one of /input-a/YYYY-MM-DD/HH00/_READY
  // or /input-b/YYYY-MM-DD/HH00/_READY is in HDFS.
  celos.orTrigger(celos.hdfsCheckTrigger("/input-a/${year}-${month}-${day}/${hour}00/_READY"),
                  celos.hdfsCheckTrigger("/input-b/${year}-${month}-${day}/${hour}00/_READY"));
  ....
  
  [source,javascript]
  
negative.code: [options="header"]
  |===
  |State|Action
  |WAITING|Call the workflow's trigger to determine whether the slot is ready.  If the trigger signals readiness, put the slot into the READY state.  If the slot has been waiting for too long, put the slot into the WAIT_TIMEOUT state.  Otherwise, keep the slot in the WAITING state.
  |READY|Pass the slot as a candidate for scheduling to the workflow's scheduling strategy.  If the strategy chooses to execute the slot, submit it to Oozie, and put it into the RUNNING state.  Otherwise, keep the slot in the READY state.
  |RUNNING|Ask Oozie for the status of the execution.  If the slot is still executing, keep it in the RUNNING state.    If the slot has succeeded, put it into the SUCCESS state.  If the slot has failed, but there are retries left, put the slot into the WAITING state again.  If the slot has failed, and there are no more retries left, put the slot into the FAILURE state.
  |SUCCESS|Do nothing.
  