Review what you are about to run
Read the Check results and confirm the playbook and named hosts. Review the predicted changes and the notes for steps a dry run cannot predict.
Some tasks can make real changes even during Check. A task that already ran during Check may do more on Apply, so do not treat it as finished work that Apply will skip.
Apply runs the playbook again
Choose Apply when you are ready, then review the app’s confirmation. Apply starts a new run of the playbook. It cannot apply a saved plan, and its result may differ from the dry run.
Review what Ansible reported after the run, including changes that were not predicted. Use the available diffs and View raw log to investigate a result you did not expect.
Stop now interrupts the run
Choose Stop now if you need to interrupt a running Check or Apply. It does not wait for a clean boundary between steps, and it does not undo changes already made.
A step may have finished on the host even if BareTold was stopped before it received the result. Treat that host’s current state as uncertain.
Check the current state after stopping
Read the stopped-run message and the available results and raw log. Review the playbook again, including any tasks that can run for real during Check, then Check the affected hosts to find out their current state.
Decide what to do next from that fresh evidence. Stopping a run is not a rollback.