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.
Recommended Order
- Read the failed Deploy, Release, or runtime status.
- Check Environment or Service logs.
- Inspect health and the affected Containers.
- Review Activity for the operation, retries, and final error.
- 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
Diagnose and correct failed Blossom deployments
Diagnose sustained application CPU pressure
Fix public Services that do not listen on the assigned port
Common issues and solutions for deploying Ruby on Rails applications on Blossom
Diagnose and correct failed Blossom deployments
Diagnose sustained application CPU pressure
Common issues and solutions for deploying Ruby on Rails applications on Blossom
Fix public Services that do not listen on the assigned port