From 8701f713047b23719bb2c24c6387b7c30e8c63fd Mon Sep 17 00:00:00 2001 From: nenizera Date: Tue, 15 Jul 2025 15:11:48 +0100 Subject: [PATCH] [SaaS] Update versioning.mdx Engage your account manager, instead of using CMS. --- .../cloudflare-for-saas/reference/versioning.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx index edddcca67c41e48..83a6fd592a38aab 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx @@ -83,7 +83,7 @@ Before your migration, you should: * `test_pending`: In the process of being verified or was unable to be verified and re-queued for verification. A custom hostname will be re-queued 25 times before moving to the `test_failed` status. * `test_active`: Passed CNAME verification * `test_active_apex`: Passed Apex Proxy verification - * `test_blocked`: Hostname will be blocked during the migration because hostname belongs to a banned zone. Contact your CSM to verify banned custom hostnames and proceed with the migration. + * `test_blocked`: Hostname will be blocked during the migration because hostname belongs to a banned zone. Engage your account manager to verify banned custom hostnames and proceed with the migration. * `test_failed`: Failed hostname verification 25 times 3. Review the results of our pre-migration tool (run by your Solutions Engineer) using one of the following methods: * Via the API: `https://api.cloudflare.com/client/v4/zones/{zone_tag}/custom_hostnames?hostname_status={status}`