Content Editing & UI Workflows

Referenced entries are not automatically published unless they are already live at the time the parent entry is published.

Root Cause

During scheduled publishing, dependencies are resolved at publish time. If a referenced entry is not live in the same environment when the parent entry publishes, it is not included automatically.

Resolution

1. Identify all referenced entries in the parent entry.
2. Schedule the referenced entries to publish first.
3. Schedule the parent entry to publish a few minutes later.

After the scheduled publish completes, open the parent entry and confirm that all referenced entries are published and visible in the target environment.

For more information, refer to Working with Nested Reference Publishing documentation.

Bulk “Add to Release” operations may remain in a queued status for an extended period or fail to complete. This behavior is identified as a platform limitation when the system experiences high concurrent load on bulk processing services.

Root Cause

High demand on background processing services can delay or block task execution.

• Symptoms: Operations may show a "queued" status for an extended time without progressing.
• Partial Success: Partial success can occur where only a subset of the selected entries are successfully added before the process stalls, if one or more selected entries do not meet the publishing requirements.
• Retry Safety: It is generally safe to retry the operation if it remains stuck, as the system will identify existing Release members and avoid duplicates.

Resolution

• Stagger Operations: Avoid triggering excessive concurrent bulk actions across the same stack to reduce service contention.
• Retry Strategy: Monitor the task status; if the operation remains queued significantly past expected limits, retry the action after platform load has stabilized.
• Batch Sizing: Reduce the number of entries per individual "Add to Release" action to ensure faster completion times.

The operation is confirmed successful once all selected entries appear within the target Release and the task status in the background activity log marks as "Completed".

Performing nested reference publishing in the Bulk Operations App may fail to show the “publish with references” option. This prevents publishing entries together with their nested references using the app.

Root Cause

The Bulk Operations App does not support the “Send with References” feature.

Resolution

1. Navigate to the Entries UI and use the Bulk Publish option for nested reference publishing.
2. Publish referenced entries separately if continuing to use the Bulk Operations App.

After navigating to the Entries UI, attempt to use the Bulk Publish feature. If the “publish with references” option is available, the correct publishing method is active.

Renaming an environment in the CMS UI may cause connectivity issues in APIs, SDKs, and the CLI when the new name is not updated. This prevents external tools from accessing the renamed environment.

Root Cause

Environment name changes affect all code or tooling references to that environment, although API tokens remain valid.

Resolution

1. Update the environment name in all API calls, SDK configurations, and CLI usage to reflect the new name.

After updating the environment name in the relevant code or tools, execute a test request. If the request connects successfully to the renamed environment, the updates are correct.