Skip to main content
addly

A known limitation should be easier to find than a sales argument.

No real product incident exists in this showcase. This register addresses each concept’s declared limitations, scope, workaround, and evidence still required.

Filter limitationsView status

Not an incident history

Each identifier describes a concept limitation or missing evidence—never an outage, an affected customer, or an invented fix.

Eight addressable limitations, linked to their path.

Filters remain in the URL. Every row has a stable permanent link and connects the concept, documentation, roadmap, and changelog traces that provide context—without claiming to resolve the limitation.

Filter the register

1 items visible out of 8.

Reset
Page SummaryEvidence required

limit-summary-templates

Compatibility with templates and page variants still requires testing

The concept shows a macro in one example page; it does not yet cover templates, restrictions, or varied content structures.

Scope
Future Confluence Cloud · pages, templates, and space restrictions
Last review
· no delivery date
Rationale
No versioned compatibility matrix exists before a testable Forge implementation.
Workaround
Treat the macro as a single placement and list every required page variant in the pilot protocol.

The format will change only when a real product exists.

A future confirmed issue will remain separate from a vulnerability and a service incident.

  • 01Verifiable product, hosting, version, and confirmation date.
  • 02Observable symptom, scope, and trigger conditions.
  • 03Tested workaround, side effects, and review owner.
  • 04Fix state without an invented delivery date.
  • 05Exact links to support, status, changelog, and corrected documentation.

A documented limitation protects better than an optimistic FAQ.

Open the relevant identifier, verify its workaround, and follow the linked work. A future outage belongs on Status; this register remains functional.

Choose an appView status