anchor.diff:  ------------------------
   // CONSOLE
   // TEST[continued]
  -
  -Now, version 2 of this policy has no `hot` phase, but if we run the Explain API again, we will see that nothing has changed.
  -The index `my_index` is still executing version 1 of the policy.
  +<1> updated `min_age` from "0ms" to "1d"
  +
  +The index `my_index` has already entered the hot phase, so it will still
  +use version 1 of the policy until it completes the hot phase.
   
   ////
   [source,js]
  
positive.code: and an index's `index.lifecycle.name` settings independently. To prevent the situation
  that phase definitions are modified while currently being executed on an index, each index
  will keep the version of the current phase definition it began execution with until it completes.
  
  There are three scenarios for examining the behavior updating policies and
  their effects on policy execution on indices.
  
negative.code: // CONSOLE
  // TESTRESPONSE[skip:no way to know if we will get this response immediately]
  
  We can update `my_executing_policy` to enter the hot phase after one day.
  
  [source,js]
  ------------------------
  