diff --git a/src/content/storybook/interactions.md b/src/content/storybook/interactions.md
index 9891e283..bf3f6f94 100644
--- a/src/content/storybook/interactions.md
+++ b/src/content/storybook/interactions.md
@@ -107,3 +107,11 @@ Interactions run as soon as the DOM loads. But external resources like web fonts
 We recommend [preloading fonts](/docs/font-loading) to ensure they're available when the DOM renders. If preloading is not possible, try adding a [delay before running interactions](/docs/delay#use-an-assertion-to-delay-snapshot-capture).
 
 </details>
+
+<details>
+
+<summary>What happens when an interaction test fails?</summary>
+
+When interaction tests fail, the story will be badged with “Failed test.” You will not be able to “pass” a build that has failed tests. Fix interaction tests in Storybook and run the build again.
+
+</details>
diff --git a/src/content/storybook/setup.mdx b/src/content/storybook/setup.mdx
index 533a7257..4aba91e6 100644
--- a/src/content/storybook/setup.mdx
+++ b/src/content/storybook/setup.mdx
@@ -378,3 +378,10 @@ If styles are not rendering correctly, there could be several reasons behind tha
 If you have additional questions, use our **in-app chat** to contact or email us at [support@chromatic.com](mailto:support@chromatic.com).
 
 </details>
+
+<details>
+<summary>What is my build failing with component errors?</summary>
+
+When a story fails to render it will be badged with “Component Error”. You will not be able to “pass” a build that has component errors. Fix story errors in Storybook and run the build again.
+
+</details>