If your Index Blocks aren't rendering assets that you feel should be included, be sure to verify whether or not you may be running into one of the following scenarios:

The 'Include when indexing' setting is disabled

Edit the asset in question and click the Configure pane. Verify that the Include when indexing option is checked. Keep in kind that in some cases, you will also need to make sure that the parent Folder of the asset in question has the same option checked.

The asset has not reached its Start Date

Edit the asset in question and click the Metadata pane. In the Start Date field, verify that the value (if filled in) contains a date that has passed. Assets who have not reached their Start Date will not be eligible for indexing or publishing until that date/time has been reached.

The asset has reached its End Date (expired)

Edit the asset in question and click the Metadata pane. In the End Date field, verify that the value (if filled in) contains a date that has not passed. Assets who have reached their End Date will no longer be eligible for indexing or publishing once that date/time has been reached.

The Index Block Depth is too shallow

Edit the Index Block and check the value for the Depth of Index field. Verify that this value is high enough to go the necessary number of levels deep within the folder hierarchy to reach the asset.

The Index Block 'Max Rendered Assets' value has been reached

Edit the Index Block and check the value for the Max Rendered Assets field. Once the Index Block renders this number of assets, it will no longer add any additional assets. To rule this out as a potential cause, try temporarily increasing this value by 500 and then check to see if the missing asset is rendered as expected. NOTE: There is a Global setting that will override this value, so it is important to verify that it is not limiting the number of rendered assets as well. See the next item in this list for information on that setting.

The 'Max Assets in Index Blocks' setting in Content Preferences is too low

Navigate to Administration > Preferences > Content > Index Blocks and check the value for the Max Assets in Index Blocks field. Verify that this number is higher than the Max Rendered Assets setting at the Index Block level. If needed, try increasing this value by 500 to see if the missing asset is then included in the Index Block.

The Index Block 'Indexed Asset Types' setting does not include the asset

Edit the Index Block and make sure that the Indexed Asset Types field is configured to include the type of asset in question.

The application is load balanced across one or more nodes and the cache is not synchronized

If the application is running in a load balanced environment, verify that your cache settings are configured properly as indicated on this page.

The Index Block Rendering Cache is not discarding properly

If none of the scenarios above allow for the asset to appear in your Index Block, you can try discarding the Index Block Rendering Cache to force a new rendering. The following steps will discard the cache:

  • Navigate to Administration > Preferences > Content > Index Blocks
  • In the Index Block Rendering Cache field, un-check the Enabled check box
  • Click Submit
  • Immediately go back into the Preferences and re-check the Enabled check box
  • Click Submit

NOTE: On systems with extremely large Index Blocks, discarding the cache can temporarily affect performance as Index Blocks throughout the system are rendered again for the first time.

If discarding the cache allows for the asset to appear in your Index Block, contact the Hannon Hill Support Team (support at hannonhill.com) so that we can troubleshoot further.

Did this answer your question?