Known issues in Content Delivery

The following list describes issues that are known to exist in Content Delivery.

High-volume publishing may result in failed Publish Transactions

Under certain conditions, high-volume publishing may result in some failed Publish Transactions. This is due to incidental conflicts that occur when the Content Data Store database is updated. Content Delivery has a fallback mechanism to deal with this problem: it retries the deployment of the content for up to 10 times. But if the number of conflicts is too high, this may not be enough.

To work around this problem, do one of the following:

  • Decrease the number of Workers in your Content Deployer configuration
  • Republish the content that failed
Publishing fails if the name of the Transport Package contains the string "66560"

If your publish action involves a very large number of transactions, the Transport Package name may be something like tcm_0-66560-66560 or tcm_0-366560-66560. In a package with this name, there are two substrings "66560": one is (part of) the transaction ID, the other denotes the type of the transaction item. The Content Deployer does not expect a transaction ID containing the string and as a result, publishing fails.

If this problem occurs, you can work around it by republishing the content that failed to publish separately. It will get a different transaction ID and publish successfully.

Context Engine Cartridge: Expression cannot refer to property defined by another expression

If you define a property in your custom vocabulary (which means the property is defined by an expression), then you cannot refer to this property from another expression that defines another property in your custom vocabulary.

Context Engine Cartridge does not work in combination with Footprint functionality in Experience Manager

Because the Footprint functionality overrides an Ambient Data Framework Claim indicating browser model, but not the user agent Claim, unexpected behavior occurs. This is because the Context Engine Cartridge determines the value of its browser.model property on the user agent.

Context Engine Cartridge CEL expressions do not support Unicode

The Context Engine Cartridge cannot evaluate an expression written using Unicode characters. To work around this problem, avoid Unicode.

Names of Context Engine Cartridge aspects and aspect properties cannot be equal to CEL reserved words
The name of an aspect or aspect property cannot be equal to a reserved word in CEL. To work around this problem, give your aspect or aspect property a different name. Specifically, your aspect or aspect property cannot be one of the following:
  • or
  • and
  • eq
  • ne
  • lt
  • gt
  • le
  • ge
  • div
  • mod
  • not
  • null
  • true
  • false
  • new
  • var
  • return