Command history
Know what ran. See what changed.
Dynomatic records the reads and writes you run from its query views, grid and jobs, with timing, items and capacity for each. A single-item edit, add or delete also keeps its before and after. While the fields it touched still hold what it left, you can undo it from the table's History.
On the 14-day trial and paid plans. Try it in Sample Mode without an AWS account.
Sample ModeUniversitySingleTable in Sample Mode. Room 102's capacity edit, 71 to 80, was committed and the query run again before the demo starts. Undo is in the table's History, Changes view, not on the global page, and writes 71 back to Sample Mode's local table, not to AWS.
Each card keeps its context. A card names the operation, the table and the workspace, with the key or expression it ran, its duration, items and capacity units. Open a write to see the fields it changed. The strip above totals read and write units for the operations history still holds.
- UpdateItem on room 102: 13ms, 1 item, 1 WCU. Changed fields: capacity.
- Read 425 RCU and Write 5 WCU across the 20 operations in history.
Each table has its own History. History mode in a table's tab lists only that table's commands, and its Changes view lists the writes that ran there. A Filters Scan that uses more than 100 capacity units, runs longer than 5 seconds or returns more than 1,000 items is marked as an expensive operation.
- History, Commands on UniversitySingleTable: 5 operations, 1 Scan, 2 writes.
- A full Scan in Sample Mode's history: 2,675 items for 308.5 RCU, marked expensive.
Undo checks the item first. Opening a change reads the item as it stands. If a field the change touched has changed since, Undo stays off, and Compare shows what the field held before, what the change left and what it holds now. Restore anyway writes the old value over the newer one.
- Room 103: capacity went 170 to 180, then to 190. Undo is off.
- Undo conflict: Before 170, After this change 180, Current 190.
Details and limits
- What Undo can reverse
- Single-item edits, adds and deletes keep a before and after snapshot. Batch writes, PartiQL writes, commits made as one transaction, writes whose images pass 64 KB and older records keep none, so they show no Undo.
- Undo is a new write
- Undo is a conditional write that restores what the change touched, and History records it as its own change, which you can undo in turn. It is not Revert, which drops a pending edit before commit.
- Production asks first
- On a production table, or one whose environment is not verified, Undo and Restore anyway ask before they write, listing each field's current value and the value it gets. On other tables Undo writes when you click.
- Not a rollback
- Undo covers single-item changes. It does not reverse scripts, agent (MCP) calls, background jobs or Copy to Table, and the grid does not refresh on its own after an undo.
- 500 entries, stars kept
- History keeps up to 500 entries. Past that, each new entry prunes the oldest unstarred one, so starred entries stay. Clear History keeps them too.
- History is not a stream
- History records what you ran in Dynomatic. A DynamoDB stream records changes from every writer to the table, within its 24-hour window and view type.