Urgent: Persistent Deployment issues please help

[plush iris]

🚨 DEPLOYMENT PLATFORM ISSUE - 100+ Credits Wasted

Job id 6355a120-4cb5-4bde-9400-e4ed5240d4ae

Issue: Persistent deployment failures with identical silent runtime failures across 5+ deployment attempts

Pattern:

✅ BUILD Phase: Always completes successfully (2.5+ minutes)
❌ DEPLOY Phase: Silent failure (no logs/errors)
❌ HEALTH_CHECK Phase: Silent failure (no logs/errors)
❌ MANAGE_SECRETS Phase: Silent failure (no logs/errors)
❌ MONGODB_MIGRATE Phase: Silent failure (no logs/errors)
Evidence This Is Platform Issue:

Working Production System: Identical code/config runs perfectly in production (https://asiaihub.com)
Code Analysis: Deployment readiness scan confirms "deployment-ready with no blocking issues"
Multiple Attempts: 5+ deployments with identical failure pattern regardless of code changes
Silent Failures: No error messages across ALL runtime phases (indicates infrastructure issues)
Configuration Verified:

✅ MongoDB Atlas connection (works in production)
✅ Environment variables properly configured
✅ CORS settings correct
✅ No ML dependencies or resource-heavy libraries
✅ Standard FastAPI + React + MongoDB stack
Impact:

100+ credits wasted on platform deployment failures
Multiple hours spent troubleshooting non-code issues
Production system delayed due to deployment platform problems
Request:

Infrastructure investigation of deployment system issues
Credit refund for wasted deployments due to platform failures
Resolution timeline for fixing deployment infrastructure
Evidence Available:

Multiple deployment logs showing identical failure pattern
Working production system proving code validity
Deployment readiness analysis confirming no code issues
This appears to be a Kubernetes/infrastructure issue on Emergent's side, not application code issues.

[glad sinew]

Hi,

Your Deployment failed issue has been resolved now and its live now.

Thanks

[plush iris]

Thank you…it would be good to know what the problem is as I think this was at the emergent end…compensation for the number of credits used to try to fix this I think is appropriate….how do I go about claiming those wasted credits?

[glad sinew]

Hi, while setting the mongourl there was a space due to which it was not reading the value correctly. In future before you redeploy cross verify once and make sure there are no leading spaces present in the values

[plush iris]

Many thanks for the reply..:whilst I appreciate the advice I would have expected the AI model to inform me that there is an invalid .env variable and as such allow me to fix this before redeploying…in this case the model went around in circles fixing issues that didn’t exist and putting debugging code in to try to ID the issue…this is clearly a flaw in the service provision….its a great service but without acknowledgement of weakness I’m inclined to tailor my approach to avoid deployment with your service…I’d appreciate the compensation as a matter of good will and improvement to the service overall. Many thanks Layth