Job Population

This article provides a potential solution for customers who have an issue with their Macro feature in general.

Other examples of issues include:

• The "Document States Report" macro no longer displays recently updated pages.

• Sometimes, it doesn’t show recently updated pages in the list.

• Sometimes, it doesn’t show the states of recently updated pages.

• Sometimes, it doesn’t show the approvers of recently updated pages.

• Document State Report Macro indicated a different status than in the document itself.

Proposed Solution

We can give the solution to the customer by executing the Job Population.

What is the Job Population?

Sometimes, it is necessary to run a population job. It updates the properties of the pages when needed to fix errors that are not processed as expected or to correct or regenerate the properties that have been modified over time. The job population is harmless but needed in some cases, as above.

Job Population Level

• The population job can be run at Space level or Instance level.

Requirements

• Enable all the workflows.

  • Enable Space Workflows in the Space tools by navigating the Document Management tab and toggling the button to activate or deactivate the workflows.

• Populating without the workflows enabled would delete the properties in the pages where the disabled workflow is linked.

Warning message while performing population

• This is a message which is prompted as the following:

Open

Possible Causes

• The message probably comes from space workflow being disabled in the space tools.

• It could be the customer has more than one workflow, and not all of them are in use.

• They might have different workflows organized by label and applied to some pages.

If the issue persists after the job population or you encounter any problem during the process, please provide the Confluence instance’s latest logs to check if the population job had any issues.