anchor.diff:  
   If you do not see a buildpack for your app, you may still be able to push your application with a [custom buildpack](../../buildpacks/custom.html) using `cf push -b` with a path to your buildpack.
   
  -### App Deploy Fails ###
  +### <a id='deploy_fail'></a> App Deploy Fails ###
   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.
   
  
positive.code: These texts explain how to prevent situations where your app builds locally but
  fails to build in the cloud.
  
    * **Verify the timeout configuration of your app.** Application health checks use
  a timeout setting when an app starts up for the first time. See [Using Application Health Checks](./healthchecks.html)
  
  ### <a id='out-of-memory'></a>App consumes too much memory, then crashes ###
  
  
negative.code: * You did not successfully create and bind a needed service instance to the app, such as a PostgreSQL or MongoDB service instance. Refer to Step 3: Create and Bind a Service Instance for a RoR Application.
  * You did not successfully create a unique URL for the app. Refer to the troubleshooting tip App Requires Unique URL.
  
  ### <a id='unique_url'></a> App Requires Unique URL ###
  <%=vars.product_short%> requires that each app that you deploy has a unique URL. Otherwise, the new app URL collides with an existing app URL and <%=vars.product_short%> cannot successfully deploy the app. You can resolve this issue by running `cf push` with either of the following flags to create a unique URL:
  
  * `-n` to assign a different HOST name for the app.
  