Skip to main content
Skip table of contents

Perform and Log Scroll Health Checks

Scroll Health Checks help Space Administrators to perform several checks on Scroll Versions related data.

These checks help to self-service and troubleshoot the spaces managed with Scroll Versions and provide better reports to the K15t Support team. Please only run the checks if you are having trouble with Scroll Versions or have been asked to run the checks by the K15t support team.

Running Scroll Health Checks 

Open Space Tools > Scroll Add-ons, click Health Checks. Once the checks have finished running, the results will be displayed. More information about each check is stored in a Scroll Health Check Log, which is automatically included in the Confluence Support ZIP.

Check results are split into four categories:

  • Manual intervention needed
  • Problems detected
  • FixMe elements found
  • Passed checks

Manual intervention needed

This category displays all failed checks that need to be further analyzed by the K15t Support Team. If you have checks displayed here, please create a Confluence Support ZIP and send it to the K15t Support Team.

Problems detected

This category displays all failed checks that can be repaired automatically. More information about these problems can be found in the Scroll Health Check Log. To repair these problems, click Repair.

FixMe elements found

This category contains all checks that need manual rework, because certain elements have been created automatically during the repair. More information about FixMe elements can be found in the Scroll Health Check Log. Please review these FixMe elements manually.

Passed checks

All successfully passed or automatically fixed checks are displayed in this category.

Available Scroll Health Checks

The following Scroll Health Checks are currently available (please note that, depending on the activated modules, the list of available checks might differ)

ShortcutNameDescriptionIf the check failsPage Revision Comment on affected pages if the check fails
L01The Scroll Lookup Index is up to date

Checks that the values in the Scroll Lookup Index are up to date with those values stored in Confluence pages and page metadata (content properties).

This check always fixes inconsistent values immediately, because all other subsequent checks rely on the correctness of the Scroll Lookup Index.

-
S01The Scroll configuration is validChecks that the Scroll Configuration (activated modules, assigned roles) can be read.

Send a Confluence Support ZIP to the K15t Support Team via help@k15t.com.

-
S02All variants refer to existing attributes
(info) Only available if the Variant Management Feature is activated.

Checks that all variants refer to existing attributes.

The check creates new attributes and values for every nonexistent attribute and references the new values in the affected variants.

  • Check the new attributes and values manually
    (info) The new attributes or values are named in the pattern 'FixMe_Attribute<no>' or 'FixMeAttribute_Value<no>'.
-
S03All preceding versions are existing

Checks that all preceding versions are existing.

The check creates a new version and saves the new version as preceding version of the affected version.

  • Check the new version manually.
    (info) The new versions are named in the pattern 'FixMe_Version<no>'.
-
S04Required add-ons for Comala integration are enabledChecks that the required add-ons for a successful Comala integration are enabled, i.e. Comala Workflows and Scroll Integration for Comala Workflows must be enabled.Enable or install the missing add-ons (info on required add-ons)
S05Comala Workflows is correctly setup to work with Scroll VersionsChecks that Comala Workflows is activated in the space, only one workflow is activated and this workflow contains the flag "versionscompleted=true" instead of "final=true".Make sure you have followed the steps on the guide to Comala Workflows integrationIf this doesn't work, contact support at support@k15t.com and provide a support ZIP.
P01All master pages have versioned pages

Checks that (at least) one versioned page exists for every master page.

The check converts affected masterpages into unversioned pages.

  • Check the affected pages.
Scroll Health Check: The page has been converted to an unversioned page by check ''P01''.
P02All versioned pages are saved on their related master page

Checks that all versioned pages are saved on their related master page.

The check moves affected pages to their related master page.

  • Check the hierarchy of the affected pages.

On versioned page: Scroll Health Check: The page has been moved underneath its master page by check "P02".

On master page (if created): Scroll Health Check: The page has been created by check "P02".

P03All versioned pages refer to existing versions

Checks that all versioned pages refer to an existing version.

The check assigns all affected pages to a new version.

  • Check the affected pages and the new version manually.
    (info) The new versions are named in the pattern 'FixMe_Version<no>'.
Scroll Health Check: The page has been assigned to the makeshift version ''<version name>'' by check ''P03''.
P04All pages have a valid Scroll Page ID

Checks that all pages have a 32-digit Scroll Page ID.

Send a Confluence Support ZIP to the K15t Support Team via help@k15t.com.

-
P05All versioned pages are saved in the correct page naming pattern

Checks that all versioned pages are saved in the correct page naming pattern (.pageTitle v<version name>).

The check changes the affected page titles to match the page naming pattern.

  • Check the affected pages.

Scroll Health Check: The page title has been changed from <previousTitle> to <newTitle> by check ''P05''.

P06All pages refer to existing attributes
(info) Only available if the Variant Management Feature is activated.

Checks that all pages refer to existing attributes.

The check creates new attributes and values for every nonexistent attribute and references the new values on the affected pages.

  • Check the new attributes and values manually.
    (info) The new attributes or values are named in the pattern 'FixMe_Attribute<no>' or 'FixMeAttribute_Value<no>'.

Scroll Health Check: The Scroll attribute values of the page have been changed to <attribute fixme name>=<attribute fixme value>, ... by check ''P06''.

P07All conditional content macros refer to existing attributes
(info) Only available if the Variant Management Feature  is activated.

Checks that all conditional content macros refer to existing attributes.

Creates new attributes, values and variants and refers to them for every affected conditional content macro.

  • Check the new attributes, values and variants manually.
    (info) The new variants, attributes or values are named in the pattern 'FixMe_Variant<no>', 'FixMe_Attribute<no>' or 'FixMeAttribute_Value<no>'.

Scroll Health Check: The Scroll attribute values of the conditional content macros have been changed to <attribute fixme name>=<attribute fixme value>, ... by check ''P07''.

P08All pages have correct translations macro structureChecks that all pages has no more than one translation macro per language. Looks also for pages with top level XHTML content that is not a translation macro.Manually removing duplicate translation macro from the storage format of the affected pages would fix the problem.-
P11Versioned pages do not have versioned child pages

Checks that all versioned pages do not have versioned child pages.

Moves affected pages in the hierarchy under the next possible master page.

  • Check the hierarchy of the affected pages.

On moved child pages Scroll Health Check: The page has been moved to be a child of <pageTitle> by check ''P11''.

P12A translated page does not have translated title for the default languageChecks that all pages have a single title for the default languageThis Check automatically removes the translated title for the original language.The translated page title ''{0}'' has been removed by check ''P12''.
P13All pages have a correct Comala state IDChecks that all pages have a workflow state id assigned and this is equal to the Comala state. This check is only executed if the Comala integration is configured for this space.Contact support at help@k15t.com and provide a support ZIP.-
P14All pages have a Scroll Page IDChecks that all pages have a Scroll Page ID. This check is only executed if duplicate page titles is the only Scroll Versions module activated in this space.Adds a valid Scroll Page ID to all affected pages.-
P15Space has a valid home pageChecks that the space has a valid home page

In versioned spaces, the home page must be either a masterpage or an unversioned page

In spaces where variant management is activated, the home page must exist in all variants

-
S101FixMe attribute values should not exist

Checks that no FixMe attribute values exist.

Review all attribute values containing 'FixMeValue' manually.-
S102FixMe attributes should not existChecks that no FixMe attributes exist.Review all attributes containing 'FixMeAttribute' manually.-
S103FixMe versions should not existChecks that no FixMe versions exist.Review all versions containing 'FixMeVersion' manually.-

Scroll Health Check Log

Scroll Health Checks automatically create a new Scroll Health Check Log for every space a check has been run in (once a log file for a space is created, every further check within the same space is written in the same log file). The logs contain more information about exceptions, violations and fixes during the Scroll Health Checks.

The logs are saved in the naming pattern scroll-health-check-<SPACEKEY>.log.csv. It can either be opened with a standard text editor or with CSV-compatible software (like MS Excel).

The log file is stored in the directory <confluence-home>/logs:

The log file contains information about all exceptions, violations and fixes occurred during each check and is automatically included in the Confluence Support ZIP.

The log file contains of the following types of log entries:

TypeDescription
REPORTInformation about the configured checks
EXCEPTIONa technical (unexpected) exception was thrown
VIOLATIONa configured check found invalid data
FIXa check fixed invalid data

For every type the corresponding page and further details are displayed:

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.