anchor.diff:  
   If your task name is unique, you can `grep` the output of the `cf logs` command for the task name to view task-specific logs.
   
  +
   ## <a id='list-tasks'></a> List Tasks Running on an App
   
   To list the tasks for a given app, run the `cf tasks APP-NAME`. For example:
  
positive.code: * Backing-up data
  * Downloading content
  
  ###<a id="task-proceses"></a> How Tasks Are Run
  
  Tasks are always executed asynchronously, meaning that they run independently from the parent app or other tasks that run on the same app.
  
  The life-cycle of a task is as follows:
  
  1. A user initiates a task in Cloud Foundry using one of the following mechanisms:
     *  `cf run-task APPNAME "TASK"` command. See the [Running Tasks](#run-tasks) section of this topic for more information.
     * Cloud Controller v3 API call. See the [Tasks](http://v3-apidocs.cloudfoundry.org/version/3.0.0/index.html#tasks) API reference page for more information.
     * Cloud Foundry Java Client. See the [Cloud Foundry Java Client Library](../buildpacks/java/java-client.html) and [Cloud Foundry Java Client](https://github.com/cloudfoundry/cf-java-client) topics for more information.
  
  1. Cloud Foundry creates a container specifically for the task.
  1. Cloud Foundry runs the task on the container using the value passed to the `cf run-task` command.
  1. Cloud Foundry destroys the container.
  
  The container also inherits environment variables, service bindings, and security groups bound to the app.
  
  <p class="note"><strong>Note</strong>: You cannot SSH into the container running a task.</p>
  
  ### Task Logging and Execution History
  
  Any data or messages the task outputs to STDOUT or STDERR is available on the app's firehose logs. A syslog drain attached to the app receives the task log output.
  
  The task execution history is retained for one month.
  
  ## <a id='manage-tasks'></a> Manage Tasks
  
  At the system level, a user with admin-level privileges can use the Cloud Controller v3 API to view all tasks that are running within an org or space. For more information, see the documentation for the [Cloud Controller v3 API](http://v3-apidocs.cloudfoundry.org/version/3.0.0/index.html#list-tasks).
  
  In addition, admins can set the default memory and disk usage quotas for tasks on a global level. Initially, tasks use the same memory and disk usage defaults as apps. However, the default memory and disk allocations for tasks can be defined separately from the default app memory and disk allocations.
  
  <% if vars.platform_code == 'PCF' %>
  <%= partial '/pcf/core/2-7/tasks_rec_alloc_pcf' %>
  
negative.code: 
  ### <a id="use-cases"></a> Use Cases for Tasks
  
  Tasks are used to perform one-off jobs, which include:
  
  * Migrating a database
  * Sending an email
  