Skip to content
ArchFoundry Docs Open the canvas

Check health and fix a failed deploy

Updated October 19, 2026Plans: Free, Pro, Enterprise

Overview

A stack that deployed is not always a stack that serves. The Health tab asks AWS, hop by hop, whether traffic reaches your app: from the internet to the load balancer, from the load balancer to the app, and whether the app is running. When a deploy or a health check fails for a reason Archie recognises, it offers a fix you can review and plan again. ArchFoundry checks only when you ask. Nothing polls.

Prerequisites

Steps

  1. Open the deployed diagram on the canvas and click the Health tab on the right. You can also click the deployed note in the top bar, or choose Check traffic… from the Deploy button's menu.
  2. Click Check traffic. ArchFoundry reads each hop from AWS.
  3. Read the verdict at the top, for example Serving with how many hops pass, then each hop below it.
  4. Where a hop fails and Archie knows why, it shows Archie can fix this with one sentence. Click Review the fix in Deploy.
  5. In Deploy, read the change, click the fix button (it names the change, ending and plan again), then review and apply the plan as usual.
  6. Click Check now afterwards to confirm the stack serves.

From the workspace, Deployments has Check health on every stack, and Review the fix when one is waiting.

Example

A healthy stack behind a load balancer reads like this in the Health tab:

text
Serving · 3 of 3 legs
Internet → edge     HTTP 200
Edge → web          the target group's health check, and each target's state
Web running         2/2 tasks, CPU 4%, 5 min

Expected result: each hop shows its own verdict, so a failure points at the hop to look at. A stack whose app fails its health check shows Not serving and names the failing hop.

Verify it worked

  • The verdict reads Serving after the fix is applied.
  • In Deployments, the stack's Health column shows the latest check.

Troubleshooting

Not serving yet. New tasks and targets take a few minutes to pass their first health checks. Check again shortly.

Nothing registered behind this. The load balancer has no healthy app behind it. Check that the service is running and its container listens on the port the card uses.

That target group is gone. The resource was removed outside ArchFoundry. Deploy again to recreate it.

This load balancer has no TLS listener. Chrome, Safari and Edge upgrade http links to https, so clicking the address usually fails to connect even though the stack serves. Check it with curl on the http address, or add a Domain card with a certificate to get an address that serves https.

The last change did not apply. The stack is as it was before. Open its diagram and click Deploy to see the reason and retry.

The card behind this target group is not on this canvas, so the fix cannot be made here. Open the diagram the stack was deployed from, then take the fix.

Could not check. The check itself failed and nothing about the deployment changed. Try again. If your session expired, sign in first.

Next steps