diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/outbound-workers.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/outbound-workers.mdx
index 340cec9d969aec1..db92e81ccc8b3bb 100644
--- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/outbound-workers.mdx
+++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/outbound-workers.mdx
@@ -81,6 +81,13 @@ export default {
 }
 ```
 
+:::note
+
+When you define parameters for an Outbound Worker in your Wrangler file, you must provide a corresponding outbound object with those parameters in your `dispatcher.get()` call. If the outbound object or its parameters are missing, your User Worker will not run and an error will be returned. 
+
+:::
+
+
 4. The Outbound Worker will now be invoked on any `fetch()` requests from a user Worker. The user Worker will trigger a [FetchEvent](/workers/runtime-apis/handlers/fetch/) on the Outbound Worker. The variables declared in the binding can be accessed in the Outbound Worker through `env.<VAR_NAME>`.
 
 The following is an example of an Outbound Worker that logs the fetch request from user Worker and creates a JWT if the fetch request matches `api.example.com`.