Known limitations
Everything on this page is current behaviour rather than a bug report. Several of these have cost somebody a day, which is why they are written down.
The two at the top are the ones that lose data.
#The two that lose data
Uninstall a standalone Capable app only after migrating. The migration reads the standalone app's content, and uninstalling deletes everything the app holds in Forge storage and Forge SQL, such as approvals and their history. The supported order is: install the suite, migrate, verify, then uninstall.
Uninstalling the suite deletes everything it holds in Forge storage and Forge SQL. That is approvals and their history, approval teams, calendar events, publishing and Sites history, and settings, so uninstall and reinstall is not a safe troubleshooting step. Atlassian can restore it for up to two weeks after the uninstall. If you uninstalled by mistake, contact Capable support straight away. After two weeks it is gone for good. Diagrams, Markdown documents, templates, saved searches and image libraries are Confluence custom content and are kept, but Capable macros do not render while the app is uninstalled. Before uninstalling, export calendars with Export as iCal or Export as CSV and keep a record of any approval history you need for audits.
#Everything else
In the Suite, a capability's own byline entry is hidden on a page until indexing has recorded that the page uses it. On a brand-new page users see only the single "Capable" byline, which reads as "the button disappeared". Standalone bylines are always visible.
The per-space "Always" option currently does nothing more than "Auto". Only "Never" changes behaviour, and a global hide always wins.
Most capabilities cannot be turned off per space at all, Export, Macros, Images, Links, Metrics, Source and Tasks show a read-only badge instead of the three-way control.
Turning a capability Visible is not enough for Sites, Quality or Forms, they stay hidden unless the edition or a feature flag also allows them, and the Capabilities tab gives no hint of this.
The nav bar and the byline menu do not apply the Advanced unlock the same way, so on some installs an Advanced capability can appear in the Capable nav but be missing from the byline menu on a page. Do not promise parity between the two.
Setting changes can take up to a minute to reach other users, and up to five minutes in a browser tab that is already open.
Global settings has no Save button. Each switch saves as soon as it is changed, from the admin page or from a capability's own Global settings entry.
While a migration is running the whole settings section bar is frozen, and the run lives in the browser tab, so navigating away or closing the tab aborts it. The banner that was meant to explain this currently renders nothing.
"Keep source macros" in the migration wizard is not a rehearsal, every migrated page renders its content twice until you re-run without it or delete the originals by hand.
Library sweeps (templates, saved searches, image libraries) can only find the old app by reading its ids off a page that still has one of its macros, so running the library step on its own after everything is converted fails with an unexplained error.
Space filters in a migration must be written as space = "KEY" or space in ("A","B"); any other form is refused outright rather than half-applied.
Turning Slack off for yourself stops your direct messages only. Slack channel posts carry on, because they belong to the channel, not to you.
Slack channel broadcasts deliberately bypass the per-user page read-permission check, so a restricted page's title and link go to everyone in the channel. Admins must understand this before wiring a space to a channel.
Slack delivery failures are silent, if the bot was never invited to the channel, or the channel was renamed or archived, messages are dropped with no error in Confluence. "Invite the bot, then send a test message" is a required setup step.
If someone's Slack or Microsoft 365 email does not match their Confluence email, their direct messages there are silently skipped.
Notification switches are scoped to one app installation, so a user running both the Suite and a standalone Approval app must switch each channel off twice.
Disconnecting Slack or Microsoft Teams is site-wide and destructive, not personal, an admin poking at the connect switch can silently switch it off for the whole company, guarded only by a browser confirmation.
Four Capable marketplace apps are NOT in the Suite: Google Analytics, Miro, Power BI and Smartsheet. Only PDF embed of the acquired embed apps made it in. Do not describe the Suite as "everything Capable sells".
The standalone Quality app declares search fields for diagrams, images, Markdown and link domains but ships nothing that fills them, so those columns are permanently empty there. Only the Suite has a fully populated Quality report.
The standalone Search app has none of the Capable CQL search fields, so it is limited to native Confluence CQL.
#Two features that are not features
An admin page banner and a page-tree browser are not available in the suite, and there is no way to switch either on. Neither is reachable.
A notification configuration screen with per-type checkboxes exists but every control is disabled and it is unreachable in every shipping app. The per-channel switches are the only notification controls.
#A few things that catch people out
The Capable Asset Store space is created automatically and must not be deleted. If creating it fails, the app will not retry for 48 hours and asset features look permanently broken.
On an unlicensed or expired site, Confluence drops product events before Capable is invoked, so indexing and approval events silently stop while the app still loads.
Content properties Capable writes onto pages are not removed on uninstall. They remain as orphaned metadata, which matters for a compliance review.
#Related
Meet them here, not in production.
