# What changed in @mastra/dynamodb

> 3 changes in @mastra/dynamodb 1 from its official release notes, upgrade guides and advisories: 1 breaking. Each one cited. Sources checked 2026-10-19. HTML: https://unstale.sh/npm/@mastra/dynamodb/

To see which of these apply to a repository, run `npx @unstale/cli init` in it.

## @mastra/dynamodb 1

### Breaking changes

- DynamoDB stores reject writes from durable agent executions that lost their run to crash recovery, preventing them from overwriting recovered messages, threads, or workflow state. Claims use the existing table; storage.prune() does not remove them yet. Requires @mastra/core 1.76.0 or… (1.4.2) — [release notes](https://github.com/mastra-ai/mastra/blob/a15924e709dd5d9439a6c102901c326ab0ec77fb/stores/dynamodb/CHANGELOG.md#142)

### Behavior and default changes

- storage.prune() now deletes durable agent run fencing records. Configure retention.workflows.runOwnership by inactivity and retention.memory.runFences by time since retirement; fences for running executions are never pruned. (1.4.3) — [release notes](https://github.com/mastra-ai/mastra/blob/a15924e709dd5d9439a6c102901c326ab0ec77fb/stores/dynamodb/CHANGELOG.md#143)

### Fixes and other changes

- Workflow step results can be recorded in the same write as workflow state, allowing evented workflows to resume with the correct state after a restart. (1.4.1) — [release notes](https://github.com/mastra-ai/mastra/blob/a15924e709dd5d9439a6c102901c326ab0ec77fb/stores/dynamodb/CHANGELOG.md#141)