From c58ccfb2c61f2978e252db8322b16aad22fa9849 Mon Sep 17 00:00:00 2001
From: "aspire-repo-bot[bot]"
 <268009190+aspire-repo-bot[bot]@users.noreply.github.com>
Date: Fri, 7 Aug 2026 04:02:36 +0000
Subject: [PATCH] docs: note that resource logs are flushed before terminal
 notifications

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---
 .../src/content/docs/testing/accessing-resources.mdx   | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/src/frontend/src/content/docs/testing/accessing-resources.mdx b/src/frontend/src/content/docs/testing/accessing-resources.mdx
index e93608236..6bd78e6bb 100644
--- a/src/frontend/src/content/docs/testing/accessing-resources.mdx
+++ b/src/frontend/src/content/docs/testing/accessing-resources.mdx
@@ -46,6 +46,16 @@ await app.ResourceNotifications.WaitForResourceHealthyAsync(
 
 This resource-notification pattern ensures that the resources are available before running the tests, avoiding potential issues with the tests failing due to the resources not being ready.
 
+<Aside type="tip">
+  If a resource fails during startup (for example, a container exits
+  immediately or an executable can't be found), Aspire flushes any captured
+  resource logs before it publishes the terminal (`Exited` or `FailedToStart`)
+  state notification. That means test code awaiting `WaitForResourceAsync`
+  with a terminal state can rely on the resource's stdout/stderr output being
+  present in the captured host logs at the point the wait completes, which
+  makes fast-failing resources easier to diagnose.
+</Aside>
+
 ## Start & Stop
 
 In some cases, you may want to manually start a resource when it is not initially started, for when the resource was created `WithExplicitStart` for example.