Revelation Documentation Email support
Reference and support

Health report and troubleshooting

Get back to modelling: check a missing element, understand an import warning or work through a failed save.

Run the Health report

Choose Menu → Health report…. It summarises model metadata and properties, duplicate IDs, missing required fields and relationship endpoints that do not resolve. Keep the panel beside the diagram while investigating, and reopen it after fixes to obtain a fresh report.

Use the report with notation knowledge: sequence fragment markers intentionally have no ordinary endpoints. A structural check is not complete BPMN or ArchiMate validation.

Common problems

SymptomWhat to check
An element is missingChoose the view of everything and All in the step bar. Inspect view membership, lifecycle visibility, containment and whether the element was actually saved.
A relationship cannot be editedIt may be derived by a scoped view. Open the underlying relationship in a more detailed view.
Drag & Drop is unavailableThe active model may exceed 300 systems or 400 interactions. Use another layout; a smaller visible view does not necessarily bypass the model count.
An import looks incompleteRead skipped/unresolved-content messages. Check the supported format/notation pair and companion DSL files. Keep the source file.
A label or line is hard to readMove elements, adjust the view, use Fit/zoom and inspect whether the diagram contains too much for one audience.
Changes disappeared after reopeningSaving a view is not saving the model. Check the actual download, GitHub commit or page attachment destination.
No Confluence Edit buttonCheck page-edit permission and loading errors; readers can use Explore.
A catalogue is staleAn editor must view the page to trigger a changed-table sync. Check selected model/view/columns and macro status.
Rovo reports an uncertain saveInspect the attached model before retrying; a write may already have succeeded.

Recover without losing more work

If the editor still contains useful unsaved work, preserve a JSON copy before refreshing or replacing it. Use a known saved file, GitHub history or attachment version when recovering. Reapply changes to a fresh model rather than repeatedly retrying a stale overwrite.

Ask for help

Include which app you use, the action, exact error, expected result and a small non-sensitive example. See contact support.