[URGENT] ■ Job ID: 906c62dd-38c3-4475-b515-0df15207c941

[dire nacelle]

■ Job ID: 906c62dd-38c3-4475-b515-0df15207c941

■ Problem

• Deployment shows "Live" status and appears successful
• However, latest code is NOT reflected in production
• Tried Re-Deploy multiple times (5+) with no improvement

■ Verification
When checking /api/health in production:
{"status":"healthy","database":"connected","timestamp":"..."}

The latest code should include a "build" field, but it's missing.
→ Production is still running old code

■ Expected behavior

• /api/health should include "build" field
• Footer should show build timestamp

■ Deploy logs
Latest deployment (d5u6p7c) shows /health returning 200 OK.
Kubernetes health check is passing.

This might be a CDN cache issue or build not being executed properly.
Please force cache invalidation or investigate the root cause.

This is urgent. Your quick assistance is appreciated.

[feral rain]

Hey 👋 thanks for the very detailed report — that level of info really helps.

Since the deployment shows Live, health checks are passing, but production is still serving old code, this strongly points to a build/cache or deployment artifact issue, not your application logic.

A few important clarifications first:

• Re-deploying multiple times won’t help if the same build artifact is being reused.
• If /api/health does not reflect the new build field, production is definitely not running the latest build.
• This is not something you can fix from the UI.

Things you can try once (if not already done):

• Run Replace Deployment (not Start Deploy) to force a full replacement.
• Confirm the updated code exists inside the /app directory (that’s what production builds from).
• Make sure no CDN caching is happening at your own domain level (if using a custom domain).

Because Kubernetes health checks are green but code is stale, this requires a server-side investigation (cache invalidation / rebuild), which we can’t perform from Discord.

Please email [email protected] and include:
• Job ID: 906c62dd-38c3-4475-b515-0df15207c941
• Live URL + Preview URL
• Confirmation that Preview shows the correct build field
• Mention that production is serving a previous build despite successful deploy

The Emergent team can force a rebuild and clear any cached artifacts safely.

We know this is urgent — thanks for your patience, and feel free to update the thread once you’ve contacted support 👍