Troubleshooting incorrect or missing statuses in the Document State Report macro in Comala Document Management Data Center App
In some cases, the Document State Report macro in Comala Document Management may show the wrong status or a null status for pages. This usually happens because the JSON content properties that the macro relies on are not updated correctly. If the JSON properties are not refreshed at the right time, the macro displays outdated or missing data.
Instructions
Set an impersonation group for data refresh
A Confluence administrator must configure an impersonation group in the global settings of Comala Document Management.
This ensures that property updates run with the right permissions, even if the user triggering the event does not have sufficient rights.
More details here: Configuration - Global | Impersonation group for Refresh Data
Run a data refresh when the data looks outdated
The data refresh process forces the JSON properties to be repopulated and reindexed.
Run the refresh at the space level to update reports.
More details here: Data Refresh - space tools
Reindex the space if needed
If data is still not correct, try running a space-level reindex.
Since reports are index-based, keeping the Confluence index current is important.
More details here: https://confluence.atlassian.com/doc/content-index-administration-148844.html
Understand the background job behavior
The scheduled job “Comala Document Management Content Properties” runs frequently but only processes events waiting to update properties.
If there are no pending updates, the job finishes almost instantly. This is expected.
Automate data refresh if required
If you want to schedule or automate the refresh, you can trigger it with a REST API call:
POST [HOST_NAME]/rest/cw/2/dataextractor/space/[SPACE_KEY]/populateReplace
[HOST_NAME]with your Confluence URL and[SPACE_KEY]with the key of the space you want to refresh.
Incorrect or missing statuses in the Document State Report macro usually happen because the JSON properties are not updated in time. Setting up the impersonation group ensures properties are always updated correctly. If data looks wrong, run a data refresh, and if necessary, reindex the space. For environments where manual refresh is not practical, the process can be automated through the REST API.