RabbinatixDocs
Sign inGet started

Manage your organization

Trash

Deleted systems, APIs, flows, logic, whiteboards, pages and spaces wait in the trash for 30 days: what goes in, who sees it, and how to restore it or delete it for good.

Open Trash in the app

What goes in the trash

When you delete one of these, it doesn't vanish at once. It waits in the trash for 30 days, with everything that went with it:

You deleteIt takes along
A systemIts APIs, other systems' expectations of it, its releases, deployments and public APIs, its logic and flows (with their test cases and runs), its health check settings and the contract watcher's settings
An APIWhat logic and test data said about it
A flowIts test cases, runs, versions and history
LogicIts versions and history, and the flows that start in it
A whiteboardIts comments, its saves (the History tab) and the drawings sent for review
A pageIts child pages, with their history, drafts and comments

The confirmation you see before a delete says so: "You can restore it from Trash for 30 days." In a project that reviews changes before publishing, deleting a system, an API, logic or a flow is a change like any other: it waits in your changes and reaches Trash once they are published. Something you added that was never published is only taken out of your changes, and nothing goes to the trash; the confirmation says which.

Some things are not kept:

  • A whiteboard's share links stop working and don't come back. Make a new link after you restore it. Its chat channels are archived with it, and restoring it opens them again.
  • A system's health results, mismatches and suggestions from the contract watcher are history, and go for good.
  • A test case or a requirement deleted on its own, and a Store package you remove, are not kept. A Store package has its own way back: import it again.
  • An API removed by publishing changes from Draft mode is not kept either: those changes were reviewed before they were published.

Find what you deleted

Open Trash in the sidebar. Each entry shows:

  • what it is (System, API, Flow, Logic, Whiteboard or Page) and its name;
  • who deleted it and when;
  • what went with it, such as "with 4 test cases and 1 test run";
  • what to restore first, when what it belongs to is in the trash too, such as the system an API belongs to;
  • how long it has left. In its last days the count turns red.

Who sees an entry

You see an entry when your role may delete that kind of thing: Edit systems for systems, Edit APIs for APIs, Edit flows for flows, Edit logic for logic, Publish whiteboards for published whiteboards, Write pages for pages, and Manage spaces for spaces. A whiteboard that was never published is its creator's alone, in the trash too. Everyone else sees an empty trash.

What an entry keeps, the copies of what was deleted, never reaches anyone's browser: the server reads it when you restore.

Restore

Click Restore next to the entry. Everything that went with it comes back as it was, under the same keys and links, and the activity log records who restored it.

Some things need something else first:

  • An API needs its system, and an expectation needs the system it calls.
  • Logic needs its system.
  • A flow needs the system it starts in and its starting logic.

When one of them is in the trash too, restore says so: restore that one first. When it was deleted for good, the entry can't come back.

What changed since the delete stays as it is. If a requirement was linked to more flows in the meantime, it keeps them and gets the restored flow back as well. If something with the same ID was made again, the new one is kept and restore tells you how many parts it left alone.

Delete for good

Click Delete for good and confirm. The entry leaves the trash and can't be restored any more.

Entries older than 30 days are deleted for good automatically, once a day. Deleting the whole organization or project empties its trash at once. See Data and privacy.