From 14dc7a554007aafe9fcc4180035feb6c78938f97 Mon Sep 17 00:00:00 2001
From: Tyson McCarney <48730964+J-T-McC@users.noreply.github.com>
Date: Fri, 6 Feb 2026 16:07:14 -0800
Subject: [PATCH] Document factoryCreateQuietly

---
 laravel/documenting/60-responses.mdx | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/laravel/documenting/60-responses.mdx b/laravel/documenting/60-responses.mdx
index faa3cc1..e13fa37 100644
--- a/laravel/documenting/60-responses.mdx
+++ b/laravel/documenting/60-responses.mdx
@@ -753,6 +753,11 @@ You can customise this process in a few ways:
 ### Changing the strategies
 You can change the order of these strategies, or remove the ones you don't need by editing the `examples.models_source` config item. By default, it's set to `['factoryCreate', 'factoryMake', 'databaseFirst']`, corresponding to the three main strategies above.
 
+
+   :::note
+   `factoryCreate` will dispatch model events resulting in listener execution which could negatively impact generation time in large event driven projects. `factoryCreateQuietly` can be used to suppress model events if they are not a requirement for your generated data.
+   :::
+
 ### Applying states
 If you want specific [states](https://laravel.com/docs/database-testing#factory-states) to be applied to your model factory, you can use the `states` field on `@apiResourceModel` or `@transformerModel`. Separate multiple states with a comma. If you're using attributes, use the `factoryStates:` argument with an array of states.