Merge branch 'production'

Author: RebeccaTamachiro

.github/CODEOWNERS

@@ -138,7 +138,7 @@
 /src/content/docs/workers/observability/ @irvinebroque @mikenomitch @rohinlohe @kodster28 @cloudflare/pcx-technical-writing
 /src/content/docs/workers/static-assets @irvinebroque @GregBrimble @WalshyDev @kodster28 @cloudflare/deploy-config @cloudflare/pcx-technical-writing
 /src/content/docs/workflows/ @elithrar @celso @cloudflare/pcx-technical-writing
-/src/content/docs/sandbox/ @whoiskatrin @ghostwriternr @cloudflare/pcx-technical-writing @ai-agents
+/src/content/docs/sandbox/ @whoiskatrin @ghostwriternr @cloudflare/pcx-technical-writing @cloudflare/ai-agents
 
 # DDoS Protection
 

src/assets/images/gateway/gateway-dns-scheduled-policies-ui.gif

@@ -10,6 +10,7 @@ import qwen from "../../assets/images/workers-ai/qwen.svg";
 import blackforestlabs from "../../assets/images/workers-ai/blackforestlabs.svg";
 import deepgram from "../../assets/images/workers-ai/deepgram.svg";
 import leonardo from "../../assets/images/workers-ai/leonardo.svg";
+import ibm from "../../assets/images/workers-ai/ibm.svg";
 
 export const authorData: Record<string, { name: string; logo: string }> = {
 	openai: {
@@ -64,4 +65,8 @@ export const authorData: Record<string, { name: string; logo: string }> = {
 		name: "Leonardo",
 		logo: leonardo.src,
 	},
+	"ibm-granite": {
+		name: "IBM",
+		logo: ibm.src,
+	},
 };

src/assets/images/workers-ai/ibm.svg

@@ -0,0 +1,20 @@
+---
+title: "Schedule DNS policies from the UI"
+description: "All users can now create and manage scheduled DNS policies directly from the Cloudflare One dashboard."
+products:
+  - gateway
+date: "2025-10-20"
+---
+
+Admins can now create [scheduled DNS policies](/cloudflare-one/policies/gateway/dns-policies/timed-policies/) directly from the Zero Trust dashboard, without using the API. You can configure policies to be active during specific, recurring times, such as blocking social media during business hours or gaming sites on school nights.
+
+- **Preset Schedules**: Use built-in templates for common scenarios like Business Hours, School Days, Weekends, and more.
+- **Custom Schedules**: Define your own schedule with specific days and up to three non-overlapping time ranges per day.
+- **Timezone Control**: Choose to enforce a schedule in a specific timezone (for example, US Eastern) or based on the local time of each user.
+- **Combined with Duration**: Policies can have both a schedule and a duration. If both are set, the duration's expiration takes precedence.
+
+You can see the flow in the demo GIF:
+
+![Schedule DNS policies demo](src/assets/images/gateway/gateway-dns-scheduled-policies-ui.gif)
+
+This update makes time-based DNS policies accessible to all Gateway customers, removing the technical barrier of the API.

src/components/models/data.ts

@@ -39,9 +39,9 @@ The Cloudflare APO WordPress plugin does not support multisite WordPress install
 
    <DashButton url="/?to=/:account/:zone/speed/optimization" />
 
-3. Go to **Content Optimization**.
-4. For **Automatic Platform Optimization for WordPress**, select **Purchase**.
-5. Enter your payment information and select **Confirm payment**.
+2. Go to **Content Optimization**.
+3. For **Automatic Platform Optimization for WordPress**, select **Purchase**.
+4. Enter your payment information and select **Confirm payment**.
 
 ## Install and activate the Cloudflare WordPress plugin
 

src/content/changelog/gateway/2025-10-20-schedule-dns-policies-from-the-ui.mdx

@@ -1,21 +1,23 @@
 ---
-title: Confirm DNS Records
+title: Confirm DNS records
 pcx_content_type: how-to
 sidebar:
   order: 6
 head:
   - tag: title
     content: Confirm DNS records
-
 ---
 
-Before you change your nameserver, confirm your DNS records are displaying correctly.
+import { DashButton } from "~/components";
+
+Before you change your nameservers, confirm your DNS records are displaying correctly.
+
+1. In the Cloudflare dashboard, go to the DNS **Records** page.
+
+   <DashButton url="/?to=/:account/:zone/dns/records" />
 
-1. Open your Cloudflare dashboard and select your account.
-2. Select your domain from the dropdown.
-3. Select the **DNS** > **Records** tile. DNS management for your domain displays.
-4. To add a record, select **Add record.**
-5. To edit an existing record, select **Edit** for the appropriate record.
-6. After making your changes, select **Save**.
+2. To add a record, select **Add record**.
+3. To edit an existing record, select **Edit** for the appropriate record.
+4. After making your changes, select **Save**.
 
 After you confirm your DNS records, [change your nameservers](/automatic-platform-optimization/get-started/change-nameservers/).

src/content/docs/automatic-platform-optimization/get-started/activate-cf-wp-plugin.mdx

@@ -21,7 +21,7 @@ You can check whether or not APO is working by verifying APO headers are present
 - `cf-edge-cache` | `cache, platform=wordpress`
   - The `cf-edge-cache` headers confirms the WordPress plugin is installed and enabled.
 
-In a terminal, use the following cURL. The header `'accept: text/html'` is important
+In a terminal, use the following cURL. The header `'accept: text/html'` is important.
 
 ```sh
 curl -svo /dev/null -A "CF" 'https://example.com/' -H 'accept: text/html' 2>&1 | grep 'cf-cache-status\|cf-edge\|cf-apo-via'
@@ -42,4 +42,4 @@ As always, `cf-cache-status` displays if the asset hit the cache or was consider
 
 ## Verify the APO integration and WordPress integration work
 
-Open your WordPress site and publish a change. When the integration is working, the page is cached with `cf-cache-status: HIT` and `cf-apo-via: tcache`
+Open your WordPress site and publish a change. When the integration is working, the page is cached with `cf-cache-status: HIT` and `cf-apo-via: tcache`.

src/content/docs/automatic-platform-optimization/get-started/confirm-dns-records.mdx

@@ -105,7 +105,7 @@ You need to register your bot and its key directory to add your bot to the list
 <Steps>
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
 2. Go to **Manage Account** > **Configurations**.
-3. Go to the **Verified Bots** tab.
+3. Go to the **Bot Submission Form** tab.
 4. For **Verification Method**: select **Request Signature**.
 5. For **Validation Instructions**: enter the URL of your key directory. You can additionally supply User Agents values (and their match patterns) that will be sent by your bot.
 6. Select **Submit**.

src/content/docs/automatic-platform-optimization/get-started/verify-apo-works.mdx

@@ -50,7 +50,7 @@ There is no fixed limit on the number of requests per browser session. A single
 
 ## Errors & Troubleshooting
 
-### I see `Cannot read properties of undefined (reading 'fetch')` when using Browser Rendering. How do I fix this?
+### `Cannot read properties of undefined (reading 'fetch')`
 
 This error typically occurs because your Puppeteer launch is not receiving the Browser binding. To resolve: Pass your Browser binding into `puppeteer.launch`.
 
@@ -83,8 +83,19 @@ Keep in mind that `page.evaluate` can only return primitive types like strings,
 
 It may be because you increased the height and width of the viewport. To fix this, increase the value of the `deviceScaleFactor` (default is 1).
 
-### I see `Error processing the request: Unable to create new browser: code: 429: message: Browser time limit exceeded for today`. How do I fix it?
+### `Error processing the request: Unable to create new browser: code: 429: message: Browser time limit exceeded for today`
 
 This error indicates you have hit the daily browser-instance limit on the Workers Free plan. [Free-plan accounts are capped at free plan limit is 10 minutes of browser use a day](/browser-rendering/platform/limits/#workers-free) once you exceed those, further creation attempts return a 429 until the next UTC day.
 
 To resolve: [Upgrade to a Workers Paid plan](/workers/platform/pricing/) which allows for more than 10 minutes of usage a day and has higher [limits](/browser-rendering/platform/limits/#workers-paid). If you recently upgraded but still see this error, try redeploying your Worker to ensure your usage is correctly associated with your new plan.
+
+### `422 Unprocessable Entity`
+
+A `422 Unprocessable Entity` error usually means that Browser Rendering wasn’t able to complete an action because of an issue with the site.
+
+This can happen if:
+- The website consumes too much memory during rendering.
+- The page itself crashed or returned an error before the action completed.
+- The request exceeded one of the [timeout limits](/browser-rendering/reference/timeouts/) for page load, element load, or an action.
+
+Most often, this error is caused by a timeout. You can review the different timers and their limits in the [REST API timeouts reference](/browser-rendering/reference/timeouts/).