diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1016.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1016.mdx
index 8e97e197140278a..59e64a424ee4ae5 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1016.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1016.mdx
@@ -32,9 +32,9 @@ Cloudflare returns a `1016` error when the [custom hostname](/cloudflare-for-pla
 
 ### Common cause
 
-- Custom hostname ownership validation is not complete. 
-- Fallback origin is not [correctly set](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/#1-create-fallback-origin). 
-- A wildcard custom hostname has been created, but the requested hostname is associated with a domain that exists in Cloudflare as a standalone zone. 
+- Custom hostname ownership validation is not complete.
+- Fallback origin is not [correctly set](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/#1-create-fallback-origin).
+- A wildcard custom hostname has been created, but the requested hostname is associated with a domain that exists in Cloudflare as a standalone zone.
 - There is no DNS record for the hostname in the Cloudflare for SaaS target zone.
 
 ### Resolution
@@ -44,4 +44,6 @@ Cloudflare returns a `1016` error when the [custom hostname](/cloudflare-for-pla
 3. The [hostname priority](/ssl/reference/certificate-and-hostname-priority/#hostname-priority) for the standalone zone will take precedence over the wildcard custom hostname. This behavior applies even if there is no DNS record for this standalone zone hostname. Use a specific hostname instead of a wildcard or [remove the standalone zone from Cloudflare](/fundamentals/manage-domains/remove-domain/).
 4. Make sure that each hostname that needs to be served by the Cloudflare for SaaS parent zone has been added as an individual custom hostname and has the status `active`.
 
+## Workers
 
+If you encounter this error with a Worker, you might be using the [Fetch API in a partial zone setup](/workers/platform/known-issues/#fetch-api-in-cname-setup).
diff --git a/src/content/docs/workers/runtime-apis/fetch.mdx b/src/content/docs/workers/runtime-apis/fetch.mdx
index 58ee6eb50768476..c1925a7af22ac75 100644
--- a/src/content/docs/workers/runtime-apis/fetch.mdx
+++ b/src/content/docs/workers/runtime-apis/fetch.mdx
@@ -72,7 +72,6 @@ async def on_scheduled(controller, env, ctx):
 </TabItem></Tabs>
 
 - <code>fetch(resource, options optional)</code> : Promise`<Response>`
-
   - Fetch returns a promise to a Response.
 
 ### Parameters
@@ -85,8 +84,8 @@ async def on_scheduled(controller, env, ctx):
       Any other `cache` header will result in a `TypeError` with the message `Unsupported cache mode: <attempted-cache-mode>`.
       _ For all requests this forwards the `Pragma: no-cache` and `Cache-Control: no-cache` headers to the origin.
       _ For `no-store`, requests to origins not hosted by Cloudflare bypass the use of Cloudflare's caches.
-			_ For `no-cache`, requests to origins not hosted by Cloudflare are forced to revalidate with
-			the origin before resonding.
+      \_ For `no-cache`, requests to origins not hosted by Cloudflare are forced to revalidate with
+      the origin before resonding.
   - An object that defines the content and behavior of the request.
 
 ---
@@ -136,3 +135,4 @@ export default {
 - [Example: cache using Fetch](/workers/examples/cache-using-fetch/)
 - Write your Worker code in [ES modules syntax](/workers/reference/migrate-to-module-workers/) for an optimized experience.
 - [Error 526](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-526/#error-526-in-the-workers-context)
+- [Fetch API in a partial setup](/workers/platform/known-issues/#fetch-api-in-cname-setup)