Skip to content

Recycle bin

Recover soft-deleted hierarchy nodes — lines, sections, assets, task points — without calling support.

Required role

Mapper or Admin.

Overview

When you delete a node in the asset hierarchy, it doesn't disappear immediately. It goes into the Recycle bin, where it stays for a retention window (default: 30 days). During that window, you can:

  • Restore — put the node back exactly where it was. Its children (if they were also deleted) come back too.
  • Delete permanently — empty the recycle bin and free the record. This is irreversible.

After the retention window, entries are purged automatically. Anything purged is recoverable only via a support case from backups.

The Recycle bin currently covers the hierarchy only (production sites, lines, sections, assets, task points). Other entities — tasks, users, repair requests, shutdowns — have their own lifecycle rules (deactivate / close / archive).

Prerequisites

  • You have the Mapper or Admin role.
  • The entry you're looking for was deleted within the retention window.

Open the recycle bin

Mapping → Recycle bin, or sometimes under Settings → Recycle bin depending on your installation.

You see a list of deleted items:

Column Meaning
Name The node's name at time of deletion.
Type Production site / Line / Section / Asset / Task point.
Path Breadcrumb of where it used to live.
Deleted by Who deleted it.
Deleted at Timestamp.
Days remaining Days until permanent purge.

Restore a node

  1. Find the entry in the list.
  2. Click Restore.
  3. Confirm.

What happens:

  • The node is put back at its original parent.
  • If the parent was also deleted, you'll be asked whether to restore the parent too (it cascades up if needed).
  • Tasks, NFC tags, schedules that were attached to the node are reattached.
  • Reports that referenced the node start showing it again.

Restored tasks don't back-fill

If a restored task had scheduled instances during the deleted window, those instances were never generated. Restoration doesn't retroactively create them.

Delete permanently

When you're certain a node shouldn't come back:

  1. Open the entry.
  2. Three-dot menu → Delete permanently.
  3. Confirm — twice. The second prompt requires typing the node name.

Permanent deletion is irreversible. The only way to get the data back afterwards is a backup-restore support case (assumes your installation retains backups, and may take a working day or two).

Bulk restore / bulk permanent delete

Select multiple rows via checkboxes, then use the bulk action bar:

  • Restore selected.
  • Delete selected permanently (with confirmation).

Useful after a mistaken bulk-delete in the hierarchy editor — restore the whole batch in one click.

What's in the bin vs what's not

Goes into the Recycle bin:

  • Production sites, lines, sections, assets, task points.

Doesn't go into the bin (different lifecycle):

  • Tasks — closed / completed / cancelled, but not deletable via the recycle bin.
  • Users — deactivated or deleted (deletion goes through the Users page, not the recycle bin).
  • Repair requests and shutdowns — closed / resolved.
  • Master data — deactivated or permanently deleted; not restorable from the bin.

Retention

Default: 30 days. Customer Admins can't change this. If you need a different retention window, raise a support case.

After 30 days, nightly cleanup:

  1. Purges entries past retention.
  2. Frees the underlying database records.
  3. Logs a retention event in the activity log.

Undoing a cascade delete

A common mistake: deleting a line also deletes all its sections, assets, and task points. If you realize the mistake quickly:

  1. Open the recycle bin.
  2. Find the line.
  3. Restore.
  4. Confirm the cascade restore when prompted — this brings the children back too.

Tasks and tags re-attach automatically. Historical reports rebind on refresh.

Common patterns

Undo a mis-click

You clicked delete on the wrong asset, caught it immediately:

  1. Recycle bin.
  2. Restore the newest entry.
  3. Done — the asset is back where it was.

End-of-project cleanup

Decommissioning an entire line you built for a trial:

  1. Delete the line from the hierarchy (it goes to the bin).
  2. Wait out the 30 days to let the recycle window protect against surprises.
  3. After retention, the entries purge automatically. No further action needed.

Panic: I permanently deleted and it's gone

Permanent deletion is irreversible from within the app. Options:

  • Check the activity log for the before-state snapshot — you can recreate the node manually from the JSON.
  • Raise a support case for a backup-restore (depending on your SLA).

Things to watch for

Permanent delete cannot be undone from the app

The "Permanent delete" button exists for a reason — sometimes you really need the data gone. Use it deliberately.

Restore parents first

If you need to restore a single task point but its parent asset is also in the bin, restore the asset first. The task point then has a place to land.

Retention is installation-level, not per-company

All companies on the installation share the same 30-day window. If your policy needs 60 or 90 days, raise it with Pegotec.

Troubleshooting

Problem Fix
Can't find the entry I deleted Check you're past its retention window — it may already be purged
Restore fails with "parent not found" Restore the parent first
Restored node doesn't appear in reports Refresh; WebSocket propagation takes a moment
Don't see the recycle bin menu Your role may not include mapping.delete — check with your Admin