Docs · Concepts
The bin
Deleting moves a thing to the bin for thirty days, from which it is restored exactly as it was, at the same address.
A delete in Mosaic is not the end of a thing. It goes to the bin, under Workspace Utilities in the sidebar, and stays there for 30 days:
What was deleted in this workspace in the last 30 days. Restoring puts a thing back as it was, at the same address; after 30 days it is deleted for good.
Restored, it comes back with the same id, so its address, its tabs, its published page and every link to it work again.
#What goes to the bin
Checks, data sources, aggregations, investigations, drilldowns, triggers, parameters, library sources, library collections and library variables, systems, agents, knowledge bases, environments, apps, integrations, workflows and monitors.
Each entry says what kind it is, what it was part of (a data source in its check), when it was deleted and by whom, and how many days it has left. Search the bin finds one by name.
#Restoring
Restore puts it back. A few things are worth knowing:
- Something inside a check needs its check first. A data source whose check is also in the bin says Its check, "Nightly till reconciliation", is in the bin too. Restore that first.
- A check comes back with its history. Its runs, exceptions and history went to the bin with it. A check whose history was too large to keep is kept without it, and the bin says so.
- Restoring is held to the licence's limits, as creating is. A plan already at its limit of checks will not restore another one.
- Workflows come back switched off. A restored workflow does nothing until somebody switches it on again, so a schedule cannot fire the moment it reappears.
- A monitor's workflows were switched off when it was deleted, and stay off when it is restored.
#Who can restore
The role that may delete a thing may restore it, and may delete it for good. A data source is an editor's, so an editor restores one; a trigger, a workflow or a system is an administrator's. Anyone in the workspace can read what is in the bin.
#Deleting for good
Delete for good removes one entry now, and cannot be undone. For a check it removes its runs, exceptions and history with it.
Empty bin deletes everything in it for good, and is an administrator's.
After 30 days, an entry is deleted for good on its own.