Publishing failures and diagnostics

During publishing to Experience Edge, the publishing job may report warnings or failed entities even when content is successfully published. These failures are often entity-level or auxiliary publishing issues (such as dictionary, translation, or associated entities) and don’t always indicate that a content item failed to publish.

This topic explains the potential publishing failure scenarios in SitecoreAI, how they are reported in the publishing job and logs, and how to assess whether a reported failure has a user-visible impact.

Potential publishing failure scenarios

Not all publishing failures prevent content from being published. Many failures are entity-specific (such as dictionary or associated entities) and allow the primary content item to publish successfully. Always verify the actual content state in Experience Edge before assuming a publish failure.

Table 1. Potential SitecoreAI entity publishing failure scenarios

Category	What failed	Does publishing continues?	User-visible impact	How to identify in logs
Dictionary / translation entities	Dictionary entities failed to publish	Yes	Content may display translation keys instead of translated text	Errors mentioning `Dictionary`, `translation`, or `SetDestinations` with Dictionary entity type
Media upload	Media blob upload failed	Partial	Media assets may be missing or not updated	`Failed to upload media blob for media item`
Batch delivery	Update, layout, or SGC batch send failed	Usually yes (partial retry)	Some items or entities may not be updated	`Sending update batch failed, Sending layout update batch failed`
Delta publish processing	Delta publish block failed and items skipped	Yes	Some items skipped during this publish	`CheckDeltaPublishBlock` errors indicating items skipped
Publishing status verification	Unable to verify publish status	Yes	Item may be skipped without confirmation	`Could not verify publishing status`
Language dependencies	Language dependency processing failed	Yes	Localized content may be incomplete	`Adding language dependencies`
Associated entities	Associated entity creation failed	Yes	Related content may be missing	`Creating associated entities`
Entity transformation	Item failed to transform into Edge format	No (entity fails)	Item may not appear in Edge	`Transforming item into a publishable Edge format`
Rendering	Rendered entity generation failed	No (entity fails)	Content may be missing or incomplete	`Failed to generate RenderedEntity`
Destination assignment	Failed to assign destination	Yes (entity-specific)	Entity not delivered to expected target	`Failed to set destinations`
Entity deletion	Layout delete entity failed	Yes	Outdated content may persist	`Sending layout delete entity failed`
Cleanup processing	Removal of outdated entities failed	Yes	Stale associated entities may remain	`RemoveOutdatedAssociatedEntitiesBlock`

Note

A reported failure does not necessarily mean that a content item failed to publish. Always verify the content state in Experience Edge before assuming a publish issue.

Do you have some feedback for us?

If you have suggestions for improving this article,