Draft changelog: Flaky Tests investigation limits

changelog/2026-08-26-browser-extension-1-0.mdx

@@ -1,8 +1,8 @@
 ---
-title: "Browser Extension 1.0.0 : Out of beta"
+title: "Browser Extension 1.0: Out of beta"
 description: "The Trunk browser extension graduates from beta with more reliable queue controls, clearer failure details, and groundwork for expanding Merge Queue beyond GitHub."
 slug: "browser-extension-1-0"
-date: "2026-08-26T00:00:00.000Z"
+date: "2026-08-26"
 category: "Merge Queue"
 type: "update"
 ---

changelog/2026-09-01-flaky-tests-investigation-limits-and-analysis-status.mdx

@@ -0,0 +1,26 @@
+---
+title: "Flaky Tests: Investigation limits and clearer analysis status"
+description: "Automatic flaky test investigations now have monthly per-repository and per-test limits, and the Analysis tab explains why an analysis was skipped or failed."
+slug: flaky-tests-investigation-limits-and-analysis-status
+date: 2026-09-01
+category: Flaky Tests
+type: update
+---
+
+**Automatic flaky test investigations are now rate-limited per calendar month, so a burst of newly flaky tests can't consume an unbounded amount of analysis.**
+
+Two limits apply, and both reset on the first of the month:
+
+| Limit                                          | Default |
+| ---------------------------------------------- | ------- |
+| Investigations per repository, per month       | 100     |
+| Investigations per individual test, per month  | 5       |
+
+What this means for you:
+
+- **Automatic and MCP-triggered investigations count.** Investigations Trunk starts when a test moves from **Healthy** to **Flaky** or **Broken**, and ones started through the [`fix-flaky-test`](/flaky-tests/reference/mcp-reference/fix-flaky-test) MCP tool, count against both limits. Only investigations that finish and produce a result are counted.
+- **Manual investigations are always available.** Investigations you start from a test's detail page in the Trunk app are exempt from both limits, even after a repository or test hits its cap.
+- **Clearer status when an analysis doesn't run.** The Analysis tab now shows a banner explaining why an analysis was skipped, such as the monthly limit being reached or a previous run still in progress.
+- **Limits can be raised.** If you expect higher volume, such as driving fixes with an agent through MCP, contact [support@trunk.io](mailto:support@trunk.io).
+
+See the [Autofix Flaky Tests docs](/flaky-tests/agents/autofix-flaky-tests#investigation-limits) for full details.

changelog/index.mdx

@@ -6,6 +6,14 @@ rss: true
 
 ## 2026
 
+### September 2026
+
+<Update label="September 1, 2026" tags={["Flaky Tests"]}>
+  **[Flaky Tests: Investigation limits and clearer analysis status](/changelog/2026-09-01-flaky-tests-investigation-limits-and-analysis-status)**
+
+  Automatic flaky test investigations now have monthly per-repository and per-test limits, and the Analysis tab explains why an analysis was skipped or failed.
+</Update>
+
 ### August 2026
 
 <Update label="August 26, 2026" tags={["Merge Queue"]}>

docs.json

@@ -633,6 +633,12 @@
           {
             "group": "2026",
             "pages": [
+              {
+                "group": "September",
+                "pages": [
+                  "changelog/2026-09-01-flaky-tests-investigation-limits-and-analysis-status"
+                ]
+              },
               {
                 "group": "August",
                 "pages": [

flaky-tests/changelog.mdx

@@ -7,6 +7,14 @@ og:title: "Trunk Flaky Tests changelog"
 
 ## 2026
 
+### September 2026
+
+<Update label="September 1, 2026" tags={["Flaky Tests"]}>
+  **[Flaky Tests: Investigation limits and clearer analysis status](/changelog/2026-09-01-flaky-tests-investigation-limits-and-analysis-status)**
+
+  Automatic flaky test investigations now have monthly per-repository and per-test limits, and the Analysis tab explains why an analysis was skipped or failed.
+</Update>
+
 ### August 2026
 
 <Update label="August 11, 2026" tags={["Flaky Tests"]}>