Skip to content

Commit 8701f71

Browse files
authored
[SaaS] Update versioning.mdx
Engage your account manager, instead of using CMS.
1 parent d5a19de commit 8701f71

File tree

1 file changed

+1
-1
lines changed
  • src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference

1 file changed

+1
-1
lines changed

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ Before your migration, you should:
8383
* `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.
8484
* `test_active`: Passed CNAME verification
8585
* `test_active_apex`: Passed Apex Proxy verification
86-
* `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.
86+
* `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.
8787
* `test_failed`: Failed hostname verification 25 times
8888
3. Review the results of our pre-migration tool (run by your Solutions Engineer) using one of the following methods:
8989
* Via the API: `https://api.cloudflare.com/client/v4/zones/{zone_tag}/custom_hostnames?hostname_status={status}`

0 commit comments

Comments
 (0)