anchor.diff:  
   <% $this_topic = 'troubleshoot-app-health' %>
   
  -See this topic for help diagnosing and resolving common issues when you deploy and run apps on Cloud Foundry.
  +See this topic for help diagnosing and resolving common issues when you deploy and run apps on <%= vars.platform_name %>.
   
   
   ## <a id='scenarios'></a> Common Issues
  
positive.code: 
  Even when the deploy fails, the app might exist on <%=vars.product_short%>. Run `cf apps` to review the apps in the currently targeted org and space. You might be able to correct the issue using the <%=vars.dev_console_2%>, or you might have to delete the app and redeploy.
  
  If you push multiple apps using a manifest and one fails to deploy, CF does not attempt to push apps specified after the app that failed. 
  
  Common reasons deploying an app fails include:
  
  
negative.code: 
  * `cf env APP-NAME`: Returns environment variables set using `cf set-env` and variables existing in the container environment.
  
  * `cf events APP-NAME`: Returns information about app crashes, including error codes. Shows that an app instance exited. For more detail, look in the app logs. For a list of <%= vars.platform_name %> errors, see [https://github.com/cloudfoundry/errors](https://github.com/cloudfoundry/errors).
  
  * `cf logs APP-NAME --recent`: Dumps recent logs. For more information, see [Viewing Logs in the Command Line Interface](./streaming-logs.html#view).
  
  