Troubleshooting Data Inconsistency: API Not Returning Correct “currentState” Value in Comala Document Management (Data Center)

Summary:
This article addresses an issue where the Comala Document Management API does not return the correct “currentState” value, resulting in data inconsistency between the Confluence UI and API responses. The steps below guide administrators through diagnosing and resolving this issue.

Environment:

• Product: Comala Document Management

• Host Product: Confluence Data Center

Problem:

• The API does not return the correct “currentState” value for pages, leading to a mismatch between the Confluence UI and API results.

• Example: The workflow state shown in the UI differs from the value returned by the API.

• Screenshots:
  1. The page status shows RELEASED

  Open

  

   

  2. The API data retrieval shows the page still in PENDING state.

Open

Cause:

• Outdated workflow content properties on Confluence pages can cause the API to return stale or incorrect state information.

• This often occurs if the content index is not up to date or if the Data Refresh task has not been run after changes.

Solution/Workaround:

1. Reindex the Affected Space:

   • Ensure all pages in the affected space are correctly indexed.

   • Follow Atlassian’s guide: https://confluence.atlassian.com/doc/content-index-administration-148844.html.

2. Run the Data Refresh Task:

   • After reindexing, run the Data Refresh task for the space.

   • Documentation: Data Refresh - space toolsPreview.

3. Configure the Impersonation Group (if needed):

   • If a non-system administrator (e.g., Space Admin) is running Data Refresh, configure the “Impersonation group for Refresh Data” to grant necessary permissions.

   • If a Confluence System Administrator runs the task, impersonation is not required.

   • Configuration guide: Configuration - Global | Impersonation group for Refresh DataPreview.

   • Note: This setting is available in Comala Document Management DC v7.6.1+.

4. If the Issue Persists:

   • Provide Confluence application and Tomcat logs for further analysis.

   • Steps:

     • Attempt to reproduce the issue.

     • Go to Create Support Zip in Confluence Admin > Troubleshooting and Support Tools.

     • Uncheck all except “Confluence Application Logs” and “Tomcat Logs.”

     • Create and attach the support zip.

     • Detailed instructions: https://confluence.atlassian.com/support/create-a-support-zip-790796819.html.

   • Also provide:

     • The exact API endpoint and parameters used.

     • Whether the issue affects all or specific pages (include URLs if specific).

     • Any recent changes to Confluence or Comala Document Management versions.

Additional Resources:

• Data Refresh - space toolsPreview

• Configuration - Global | Impersonation group for Refresh DataPreview

• Release notes 7.6.1 | Impersonation group for Refresh DataPreview

• https://confluence.atlassian.com/doc/content-index-administration-148844.html

• https://confluence.atlassian.com/support/create-a-support-zip-790796819.html

Note:
If you require further assistance, please provide the requested logs and details to Appfire Support for deeper investigation.