In Atlassian Connect, the content_updated webhook fired whenever any aspect of custom content changed, including updates to content properties (via the Content Properties API). This allowed apps to react to property changes in real time.

In Forge, the equivalent event avi:confluence:updated:custom_content only fires when the body of the custom content is modified. Updates made exclusively to content properties do not trigger this event, leaving no way for Forge apps to react to property-only changes made by other actors.

Use case:
Apps that store state or metadata in content properties (e.g., tracking completion, scores, or configuration per content item) currently have no Forge event to react to when those properties are updated externally. This is a regression compared to the Connect content_updated webhook behaviour.
Expected behaviour:
avi:confluence:updated:custom_content should fire (or a new dedicated event such as avi:confluence:updated:custom_content_property should be introduced) whenever content properties on custom content are created, updated, or deleted.

Workarounds today:
None fully viable. Apps can track property changes at write time if they control all writes, but cannot react to changes made by other actors.