Undo and recovery

Most of what you do in Jootle is reversible. This chapter is the practical guide to undoing the operations that come up.

The general pattern

Three layers, in order of preference:

1. Conversational undo. Tell your AI: “undo that”. Works for many recent actions, especially ones it just performed.
2. Trash / archive. Most deletions go through a soft-delete state first. You can restore from there for a window of time.
3. Backup restore. For items that aged past the soft-delete window or for full-instance rollback. See Backups and recovery.

You don’t have to memorize which one applies; ask your AI to recover the thing, and it’ll pick the right layer.

Undoing recent actions

For things that happened in the last few minutes or this conversation:

“Undo that last email send.”

“Cancel the calendar event we just created.”

“Reverse the task assignment to Mike.”

If the action is reversible (the email hasn’t been read, the calendar invite hasn’t gone out to the other party), your AI rolls it back. If not, it tells you what’s possible (e.g., “I can send a correction email” or “the calendar event is already on Anna’s calendar; you’d need to delete it and notify her separately”).

Some specific reversibilities:

• Email sent. Not literally undoable, but your AI can draft a correction or retraction.
• Calendar event created. Reversible by deletion, with a notice to attendees.
• Task created. Always reversible by deletion.
• Artifact produced. Reversible by deletion; the previous version is in the artifact’s history.
• Memory written to the knowledge graph. Reversible: “Forget that I said X.”
• Permission change. Reversible.
• Toolkit installed. Reversible: uninstall.

Restoring deleted items

When you delete something in Jootle, it goes to Trash (or Archive for things that prefer that term, like contacts and projects).

You can find recently deleted items under each kind of entity:

• Settings → Trash for instance-wide recently-deleted items.
• A project’s Archive for archived projects.
• A toolkit’s Trash for items deleted from within that toolkit.

Items in Trash can be restored with a click. The restore window is typically 30 days; after that, items move to backup storage and the restore path goes through support.

Restoring something from days ago

For items older than the Trash window but within the backup retention period (see Backups and recovery):

Self-service for the past 24 hours, via your AI:

“Restore the artifact I deleted yesterday on the kitchen project.”

For older items, email support@jootle.com with what you want restored. We can usually pull from backup within a few hours.

Restoring a whole project or program

If you deleted (or archived) a whole project, the project’s contents — tasks, lists, artifacts, chat — are bundled with it. Restoring the project restores everything that was in it.

If the project was deleted within the Trash window, restore from there. Older than that, it’s a support request.

Recovering accidentally-erased memories

The knowledge graph has its own undo. If you said “forget X” and then realized you didn’t mean it:

“Restore the memory you just erased about X.”

Your AI re-adds the entity or relationship to the knowledge graph. This works for recent erasures (the same conversation, generally).

For erasures from days ago, your AI may not be able to recover automatically; you’d re-state the fact (“X is still true; remember that”). The end result is the same.

Recovering a whole instance state

For “I want everything as of last Tuesday at 3pm”:

• Within the last 24 hours: ask your AI; it can produce a per-item summary of what’s changed and offer to selectively roll back.
• More than 24 hours: contact support for a full restore. Usually we offer a side-by-side restore (a new instance with the restored state, your current instance untouched, so you can compare) before any overwrite.

Full restores are rare. They come up when:

• You ran a bulk operation that did the wrong thing across many items.
• An automation produced bad output across many entities.
• You want to revert a deployment of a major change.

What’s NOT recoverable

A few things that are gone-gone once removed:

• Items deleted more than the maximum backup retention window (1 year for monthly archives on Business+; 90 days for weekly archives on lower tiers).
• API keys and credentials intentionally removed. The encrypted-at-rest copy is gone once you rotate; the new key doesn’t auto-restore the old one.
• External actions that already happened in the real world. A sent email that the recipient already read; a payment that was already processed at a third party. The Jootle record can be restored but the real-world effect cannot.

These are worth knowing about. For the first two, the right preventative is the periodic export (Data, privacy, and exports). For the third, the preventative is the approval gates.

A few “I broke it” patterns and the fix

“I told my AI to delete all my emails for last year. I didn’t really mean all of them.”

Email deletion at Gmail’s end is reversible (Gmail’s Trash holds for 30 days). Recover from Gmail’s Trash. Lesson: bulk destructive actions should always go through a gate, even if you’d normally loosen for routine ones.

“I uninstalled a toolkit and now I want it back.”

Reinstall it. Your data was preserved by default. If you ALSO ran “delete this toolkit’s data” after uninstall, the data is gone; the toolkit reinstalls fresh.

“I deleted a project I shouldn’t have.”

Trash → restore. If older than 30 days, support.

“I changed a setting and now things are weird.”

Settings have a per-page history. Settings → [the page] → recent changes. Revert from there. If the bad change was the whole-instance one (toolkit configuration, AI provider configuration), recovery may need support.

The patience principle

Most of these recoveries work better if you don’t panic. The customers who do the most damage in a recovery scenario are the ones who try to “fix” multiple things at once and end up tangling state.

The right move when you realize something went wrong:

1. Stop doing things.
2. Check the Activity log for the timeline.
3. Decide what you want the end state to be.
4. Ask your AI (or support) for the cleanest path.
5. Do one thing.
6. Verify.
7. Decide if you need another step.

That’s slower than panicking but much more likely to end in the state you wanted.