anchor.diff:  with no indication of error in the UI.  The log however, will contain
   the error.
   
  +==== The Celos name
  +
  +The link:http://www.quicksilver899.com/Tolkien/LOTR/LOTR_AC.html[_Lord
  +of the Rings dictionary_] defines it as:
  +
  +....
  +Celos S; also Kelos; freshet; kel- flow away [Sil; *kelu-]; one would
  +want to choose los snow [Sil] for the final element, but the text of
  +Unfinished Tales, Index, entry Celos states the final form derives
  +from Q -sse, -ssa, a form of emphasis [some say locative], making the
  +definition 'much flowing' or 'freshet', often resulting from melting
  +snow; perhaps 'snow' is then implied from the ending; a river in
  +Gondor
  +....
  +
  +Alternatively, the
  +link:http://programmingisterrible.com/post/65781074112/devils-dictionary-of-programming[_Devil’s
  +Dictionary of Programming_] defines it as:
  +
  +....
  +Configurable: It’s your job to make it usable.
  +Elegant: The only use case is making me feel smart.
  +Lightweight: I don’t understand the use-cases the alternatives solve.
  +Opinionated: I don’t believe that your use case exists.
  +Simple: It solves my use case.
  +....
  +
   === Related Tools
   
   Two similar, programmable schedulers:
  
positive.code:         02:00:00.000Z
  ....
  
  === Continuous Delivery of Workflows
  
  Changing a workflow definition in Celos is as simple as updating the
  
negative.code: 
  === Notes
  
  ==== Time
  
  All times in Celos use the UTC timezone exclusively.
  
  ==== Weaknesses of the Celos architecture
  
  ===== Single master
  
  This might not be as bad as it sounds.  The reason is that during
  normal operation, most workflows will usually be mostly successful.
  