Skip to content

Commit bad3ce8

Browse files
Merge branch 'production' into maddy/email-security-pcx-18362
2 parents be53ab2 + 980628f commit bad3ce8

File tree

3 files changed

+7
-3
lines changed

3 files changed

+7
-3
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -111,8 +111,8 @@ Consider the following solutions:
111111

112112
## Custom hostname fails to verify because the zone is held
113113

114-
The [zone hold feature](/fundamentals/account/account-security/zone-holds/) is a toggle that will prevent their zone from being activated on other Cloudflare account.
115-
When the option `Also prevent subdomains` is enabled, this prevents the verification of custom hostnames for this domain. The custom hostname will remain in the `Blocked` status, with the following error message: `The hostname is associated with a held zone. Please contact the owner of this domain to have the hold removed.` In this case, the owner of the zone needs to [release the hold](/fundamentals/account/account-security/zone-holds/#release-zone-holds) before the custom hostname can become activated.
114+
The [zone hold feature](/fundamentals/account/account-security/zone-holds/) is a toggle that will prevent their zone from being activated on other Cloudflare account. When enabled, Cloudflare is not able to issue an SSL/TLS certificate on behalf of that domain name for either a zone or custom hostname.
115+
When the option `Also prevent subdomains` is enabled, this prevents the verification of custom hostnames for this domain. The custom hostname will remain in the `Blocked` status, with the following error message: `The hostname is associated with a held zone. Please contact the owner of this domain to have the hold removed.` In this case, the owner of the zone needs to [release the hold](/fundamentals/account/account-security/zone-holds/#release-zone-holds) before the custom hostname can become activated. After the hostname has been validated, the zone hold can be enabled again.
116116

117117
## Hostnames over 64 characters
118118

src/content/docs/cloudflare-one/email-security/detection-settings/configure-text-add-ons.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,10 @@ You can create custom labels to be used as the subject or body prefix for emails
1111
You can only configure text add-ons if you deploy Email Security via [MX/Inline](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment/).
1212
:::
1313

14+
:::caution
15+
If you currently do not have text add-ons enabled, configuring text add-ons will add a banner to the subject line. As a result, the subject line and the email body will be reduced.
16+
:::
17+
1418
## Subject prefix
1519

1620
To configure a subject prefix:

src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,4 +74,4 @@ Objects in the **hibernated** state keep their Websocket clients connected, and
7474

7575
The next incoming request or event starts the cycle again.
7676

77-
As explained in [When does a Durable Object incur duration charges?](/durable-objects/platform/pricing/#when-does-a-durable-object-incur-duration-charges), a Durable Object incurs charges only when it is **actively running in-memory**, or when it is **idle in-memory and non-hibernateable**, the two states highlighted in red in the above diagram.
77+
As explained in [When does a Durable Object incur duration charges?](/durable-objects/platform/pricing/#when-does-a-durable-object-incur-duration-charges), a Durable Object incurs charges only when it is **actively running in-memory**, or when it is **idle in-memory and non-hibernateable**.

0 commit comments

Comments
 (0)