> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Delete or Archive a Task: Which One Should You Use?
- URL: https://blog.jestor.com/delete-or-archive-a-task/
- Published: 2026-09-17T22:28:55.000Z
- Updated: 2026-09-17T22:28:55.000Z
- Author: Bruno Bannach

Choosing whether to **delete or archive a task** depends on whether you want the record gone or simply out of the way. Archiving preserves history; deleting removes the item entirely.

## Why the distinction matters

Tasks are often cancelled rather than completed, and treating cancellation as deletion loses information you may want later.

- No record that a piece of work was planned and dropped
- Throughput figures distorted by removed items
- Reversing a mistaken deletion becoming a recovery exercise
- Dashboards that disagree with what people remember happening

## Comparing the options

| Action           | Effect                                            | Use when                                       |
| ---------------- | ------------------------------------------------- | ---------------------------------------------- |
| **Archive**      | Removed from the active table and from the charts | The work was dropped but should stay on record |
| **Mark ignored** | Kept with a status showing it will not be done    | You want the reason visible in the pipeline    |
| **Delete**       | The task is removed                               | The record was created in error                |

## How to do it in Jestor

1. Open the task in **Jestor**.
2. To keep it on record, change its status to archived — it leaves the active table and the charts.
3. To show it was consciously dropped, set the status to ignored instead.
4. To remove it entirely, open the three-dot menu and choose to delete the task.
5. Check the table history view if you need to confirm what was deleted and by whom.

## Why choose Jestor for reversible operations?

**Jestor** keeps a recycle bin that recovers records and fields deleted by accident, so an irreversible action is less irreversible than it sounds.

The table history view records deletions with their source — a user, an automation, or the **API** — which means an unexpected removal can always be traced.

## Frequently Asked Questions

### Can I recover a deleted record?

The recycle bin recovers deleted records and fields. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Does archiving affect my charts?

Yes, archived tasks are removed from the active charts.

### Can I see who deleted something?

Yes, in the table history view, filtered by action and source.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.