Self-manage backups feature limitations and workarounds

Note: This feature is now available in early access and has some functional limitations.

This page lists the limitations and workarounds, where available, for the Self‑manage backups feature. Review these details before using the feature.

Limitations

Trial Balance Sync engagements

If you restore an engagement that is used as the source in a Trial Balance Sync:

  • The link between the source and destination engagements breaks.

  • Syncing stops immediately.

  • No warning notification is displayed during the restore process.

Note: Restoring the destination engagement in a Trial Balance Sync will not break the linkage and that will continue to sync changes from the source.

Workaround

  • In the destination engagement, unlink the Trial Balance Sync.

  • Re‑import the trial balance from the same Caseware Cloud engagement.

  • Re‑enable the Trial Balance Sync.

This restores the destination engagement’s connection to the updated data.

Consolidated linked engagements

If you restore an engagement that participates in a consolidated engagement (as either a linked parent or linked subsidiary):

  • The consolidation link is lost.

  • Updates no longer sync to the consolidated engagement.

  • No warning notification is displayed during restore.

Note: Restoring the consolidated engagement itself does not break the consolidation links.

Workaround

  • Remove the link to the other engagement.

  • Re‑add the link after the restore is complete.

Central Planning engagements

If the Central Planning (CP) engagement is restored:

  • All links to destination engagements break.

  • These linkages cannot currently be restored.

Note: Restoring the destination engagement does not break the link to the Central Planning engagement but users may need to ensure the CP hub changes are re-synchronized.

Workaround

  • There is currently no workaround available to restore linkages when the CP engagement itself is restored.

Transactions and embedded analytics

Backups do not include:

  • Transactions

  • Embedded analytics data

As a result:

  • Analytics always reflects its current state, not the state at the time of backup.

  • Transaction and analytics data are not restored during a restore.

  • During backup creation, users are shown a warning dialog if the engagement contains transactions or embedded analytics.

Workaround

  • There is currently no workaround for this limitation.

For full details on the self-manage backup feature, see Self‑manage backups.