Undo and recover changes
Reverse eligible Assistant changes and understand what recovery preserves.
Use Undo on an eligible applied change or enter /undo to request reversal of the last change in the conversation. Strive checks whether the item can still be reversed without overwriting newer work.
What can be recovered
An app in Trash can be restored while it is retained. An app or workflow definition can be restored from a saved version. A remembered fact can be recreated after being forgotten. Reversal is specific to the object and operation; it is not a rewind of the entire workspace.
For example, restoring a workflow recipe does not retract emails or webhook requests a previous run sent. Restoring an app definition does not restore rows deleted from a data source. A newly created public link is different from the revoked one.
When Undo is refused
Another person or process may have changed the object since the original action. Strive avoids overwriting that newer state. Read the current version, compare it with the earlier one, and decide which parts should be restored.
Some actions never have automatic Undo: permanent connection or record deletion, consumed processing, cancelled runs, and operations without a reliable version check. Their cards identify this limitation.
Recover deliberately
- Identify the original action and its target.
- Check the current app, workflow, or operation state.
- Use Undo if it remains available and its effect is appropriate.
- Otherwise use app Trash, app version history, or workflow versions.
- Verify the restored item and its next run before sharing it again.
If an answer or request timed out, inspect its saved result before trying to reverse or repeat it. An uncertain outcome is not proof that nothing changed.