Issue Summary

This ticket is a result of a discussion with Xiao Ma on the Confluence Cloud team at AtlasCamp 2026. He asked me to file a ticket here so that it could be routed to his team. This bug prevents seamless and timely upgrades of Connect content properties to Forge content properties.

I ran this issue by Sean Bourke and he suspects that the issue was caused by something on the Confluence side, wherein CQL reindexing is not kicked off immediately upon installation of the module.

Steps to Reproduce

Content property modules on Confluence Cloud fail to deploy to the tenant within a reasonable amount of time if the content properties are declared using Forge modules. If I define comparable content property modules using Connect-on-Forge instead, and if I deploy the Forge and the Connect-on-Forge modules at the same time, the Connect-on-Forge modules are installed immediately and consistently, whereas the Forge module takes a long time to register. I timed this scenario and it sometimes takes an hour to register properly.

The behavior is different depending on whether the Forge app is a new install, or if it is an upgrade that adds new content property modules to an existing app:

• For new Forge app installs, both Forge and Connect-on-Forge modules are installed immediately and searching works correctly.
• For a minor version app upgrade that adds new content property modules to an existing app, the Connect-on-Forge module is installed immediately but the Forge module takes a long time to register before it becomes usable, so the Forge module is not searchable by its index.

This behavior occurs within a single Connect-on-Forge app that has module definitions similar to the following:

modules:
  // ...
  confluence:contentProperty:
    - key: native-cprop
      propertyKey: 'nativeindex'
      values:
        - path: 'nco'
          type: 'string'
          searchAlias: 'nativesearch'
connectModules:
  confluence:confluenceContentProperties:
    - key: cof-cprop
      name:
        value: COF CProp
      keyConfigurations:
        - propertyKey: cofindex
          extractions:
            - objectName: cof
              type: string

When I say that the Forge module does not appear to be registered, what I mean is that I receive an HTTP 400 when trying to use CQL to search the indexed content property. For example, with the above modules, I would attempt to run the following two CQL searches:

content.property[nativeindex].nco=true
content.property[cofindex].cof=true

 
The cofindex query would return success, while the nativeindex search would return HTTP 400 until the module is finally installed.

Expected Results

 h3. Actual Results

(see table under Expected Results)

Workaround

none