Blossom Docs
Blossom

Troubleshooting

Diagnose application problems from Product-level evidence

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.

  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

Debug Failed Deployments

Diagnose and correct failed Blossom deployments

Debug High CPU Usage

Diagnose sustained application CPU pressure

Web Service Port

Fix public Services that do not listen on the assigned port

Debug Rails Deployments

Common issues and solutions for deploying Ruby on Rails applications on Blossom

Debug Failed Deployments

Diagnose and correct failed Blossom deployments

Debug High CPU Usage

Diagnose sustained application CPU pressure

Debug Rails Deployments

Common issues and solutions for deploying Ruby on Rails applications on Blossom

Web Service Port

Fix public Services that do not listen on the assigned port

On this page