anchor.diff:  ---
   ## <a id="active"></a> Currently active tasks
   
  -At any time the Director may be performing multiple tasks at once. Active tasks can be in two states: `queued` or `processing`.
  +At any time the Director might be performing multiple tasks at once. Active tasks can be in two states: `queued` or `processing`.
   
   To see all currently active tasks:
   
  
positive.code: Total tasks running now: 2
  </pre>
  
  <p class="note">Note: <code>--no-filter</code> flag shows all tasks. Without that flag, the Director returns a subset of running tasks that it deems important.</p>
  
  ### <a id="join-active"></a> Joining tasks
  
  Since Director tasks continue to run in the background, even if the CLI has disconnected, you can rejoin a task at any time:
  
  <pre class="terminal">
  $ bosh task 766
  
negative.code: title: Director tasks
  ---
  
  An operator uses the CLI to interact with the Director. Certain CLI commands result in complex and potentially long running operations against the IaaS, blobstore, or other resources. Such commands are associated with a Director task and continue running on the Director even if the CLI disconnects from the Director.
  
  To find out if a CLI command has an associated Director task, look for "Director task [NUM]" in its output:
  
  <pre class="terminal">
  $ bosh deploy
  