Technical limitations

Limits (and defaults)

Please see Limits and Defaults for details.

Contentful compatibility restrictions

Please see Contentful compatibility for details.

Known issues

Breaking change: production cluster launch

Affects: All APIs

After this initial production release, breaking changes will not be added retroactively to existing accounts in production. Breaking changes will only be added to new accounts, upon request, or when requests are explicitly made to a newer API version.

Index preservation in reference lists

Affects: Satellite APIs

We expect that referenced entries may not load. This may be due to a lack of permissions or referenced content being removed or unpublished. When you create lists of references, the index within them may be relevant. E.g., a column’s property may need certain elements at a certain position. If one of the references cannot be resolved, we return null for the item. While this helps in some edge cases, it is not what most developers would want for most fields. That’s why we’re adding an option to ignore indices and, instead, return a list of all references that can be resolved without null values. This changes the typing of reference list properties from (AnyEntry | null)[] to just AnyEntry[].

Paragraphs library item references

Affects: Satellite APIs

Paragraph library items are currently nested and don’t need to be, which simplifies working with them as a front-end developer. Instead, we will treat the content as a direct descendant so that as a front-end developer, you don’t have to care about whether a paragraph is shared or not.

Limited support for private files

Affects: Satellite APIs

Files from Drupal are treated equally, regardless of whether they’re in the private or public file directory. Instead, we will allow developers to either opt in to this behavior or, as a fallback, only provide private files as preview assets, meaning that they’re not publicly available unless a user is granted permission explicitly.

Fixed asset domains

Affects: Asset APIs

Assets are currently served directly from their bucket URL. This will be changed to a custom domain to remain flexible for future provider changes for enterprise customers needing to whitelist asset download domains. If you are not whitelisting our domains, this won’t affect you.

With this change, different domains will serve different types of content, e.g., for streaming videos or serving images.

No type inheritance

Affects: Satellite APIs, Content Management API

Types are flat right now, meaning they don’t share properties. Sharing properties can simplify some implementations where many types have the same base properties. We are going to include 1-level type inheritance. By default, we will use the type from Drupal as the parent type and then add bundles as the child type. This can be customized to optionally include additional fields in the parent type if they exist at multiple bundles.

This won’t affect content queries but may require different handling in the Content Management API and content type API for satellites.

Circular type dependencies are not supported

Affects: Content Management API

If Drupal types have a circular dependency to themselves (e.g., node type A links to node type B that links back to node type A), the types are not propagated. This does not affect most customers, and we are looking for ways to support these use cases.

The image API sometimes returns 415 Unsupported Media Type

Affects: Image API

For some webp-based assets, the image API may return a 415 Unsupported Media Type. Please let us know if you encounter this issue.

Panelizer: Basic support only

The panelizer structure is currently served as is (JSON). We are going to optimize this to simplify the structure for use outside of Drupal.

Acquia Site Studio: Basic support only

The Site Studio content structure is currently served as-is (JSON). We are going to optimize this to simplify the structure for use outside of Drupal.

User data stores don’t allow links

The link type is currently not supported for user data stores. This could be useful to link multiple content entries together (e.g. taxonomy terms to content, per user).

Previews require push

Drafts are currently generated when content is saved in an unpublished state in Drupal (if allowed by the Flow config). We want to optimize this to allow editors to hit Preview in Drupal and be able to see a preview of the content in any connected frontend without explicitly saving the content in Drupal.

Opt-in features

These features must be enabled explicitly by our support team. Please reach out to us if you are interested in using them.

Search

While the search feature is generally enabled on all environments, we don’t index fields by default. If you want your Content Cloud to, e.g., index HTML fields, we can enable that for you.

Custom User Data

User data stores are disabled by default. If you want to use them, please reach out to us.

Restricted features

These features are only available for certain accounts or usage types. Please reach out to us to learn more about them.

CDN

The CDN API is currently only available for production spaces. For testing the Content Cloud, please use the Live API instead.

Multiple environments

We create a default prod environment when adding Content Cloud spaces. Please use this environment for all testing purposes. If you would like to manage multiple environments for a space, please reach out to our support.

Global replication

Our global replication feature is only available for production spaces. If you are interested in this feature, please contact our support team.

Environment aliases

Environment aliases are only available for production spaces. If you are interested in this feature, please contact our support team.