---
title: Troubleshooting
url: "/docs/debug/"
canonical_url: https://docs.blossom88.com/docs/debug/
markdown_url: https://docs.blossom88.com/docs/debug.md
summary: Diagnose application problems from Product-level evidence
categories:
- debugging
- troubleshooting
- support
---

# Troubleshooting

Start with the Product that needs attention. Blossom combines application
evidence with the high-level result of its managed operations so you can decide
whether to fix the App, retry, wait for automatic recovery, or resolve a
blocker in your cloud account.

## Recommended Order

1. Read the failed Deploy, Release, or runtime status.
2. Check Environment or Service logs.
3. Inspect health and the affected Containers.
4. Review Activity for the operation, retries, and final error.
5. Correct application configuration, source, credentials, quota, or billing
   only when Blossom identifies it as customer-actionable.

When Blossom identifies a platform-owned failure, contact support with the
Product identifier and Activity identifier. That evidence lets support follow
the same operation without asking you to diagnose the platform.

## Guides

<div class="grid grid-cols-1 md:grid-cols-2 gap-4 mb-4">


  
  
<div class="p-4 border rounded-lg shadow-sm">
  <a href="/docs/debug/deploy-failures/" class="text-indigo-600 hover:text-indigo-800 hover:underline font-medium">Debug Failed Deployments</a>
  <p class="text-sm text-gray-600 mt-1">Diagnose and correct failed Blossom deployments</p>
</div>
  

  
  
<div class="p-4 border rounded-lg shadow-sm">
  <a href="/docs/debug/high-cpu/" class="text-indigo-600 hover:text-indigo-800 hover:underline font-medium">Debug High CPU Usage</a>
  <p class="text-sm text-gray-600 mt-1">Diagnose sustained application CPU pressure</p>
</div>
  

  
  
<div class="p-4 border rounded-lg shadow-sm">
  <a href="/docs/debug/web-server-port/" class="text-indigo-600 hover:text-indigo-800 hover:underline font-medium">Web Service Port</a>
  <p class="text-sm text-gray-600 mt-1">Fix public Services that do not listen on the assigned port</p>
</div>
  

  
  
<div class="p-4 border rounded-lg shadow-sm">
  <a href="/docs/debug/rails/" class="text-indigo-600 hover:text-indigo-800 hover:underline font-medium">Debug Rails Deployments</a>
  <p class="text-sm text-gray-600 mt-1">Common issues and solutions for deploying Ruby on Rails applications on Blossom</p>
</div>
  

  
  
<div class="p-4 border rounded-lg shadow-sm">
  <a href="/docs/debug/deploy-failures.md" class="text-indigo-600 hover:text-indigo-800 hover:underline font-medium">Debug Failed Deployments</a>
  <p class="text-sm text-gray-600 mt-1">Diagnose and correct failed Blossom deployments</p>
</div>
  

  
  
<div class="p-4 border rounded-lg shadow-sm">
  <a href="/docs/debug/high-cpu.md" class="text-indigo-600 hover:text-indigo-800 hover:underline font-medium">Debug High CPU Usage</a>
  <p class="text-sm text-gray-600 mt-1">Diagnose sustained application CPU pressure</p>
</div>
  

  
  
<div class="p-4 border rounded-lg shadow-sm">
  <a href="/docs/debug/rails.md" class="text-indigo-600 hover:text-indigo-800 hover:underline font-medium">Debug Rails Deployments</a>
  <p class="text-sm text-gray-600 mt-1">Common issues and solutions for deploying Ruby on Rails applications on Blossom</p>
</div>
  

  
  
<div class="p-4 border rounded-lg shadow-sm">
  <a href="/docs/debug/web-server-port.md" class="text-indigo-600 hover:text-indigo-800 hover:underline font-medium">Web Service Port</a>
  <p class="text-sm text-gray-600 mt-1">Fix public Services that do not listen on the assigned port</p>
</div>
  

</div>