# Command deduplication persistence

**URL:** <https://forum.canton.network/t/command-deduplication-persistence/231>\
**Category:** App Development\
**Created:** [April 24, 2020, 9:56am UTC](https://forum.canton.network/t/command-deduplication-persistence/231 "2020-04-24T09:56:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![georg](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/georg/32/368_2.png) [@georg](https://forum.canton.network/u/georg)\
**Post date:** [April 24, 2020, 9:56am UTC](https://forum.canton.network/t/command-deduplication-persistence/231/1 "2020-04-24T09:56:28Z")

</div>

If I run the sandbox with persistence turned on, will it persist its command id deduplication cache, or is it only kept in memory? If it’s persisted, I suppose it will “recover” the deduplication state upon restart?

---

<div class="post-metadata">

**Author:** ![stefanobaghino-da](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/stefanobaghino-da/32/7057_2.png) [@stefanobaghino-da](https://forum.canton.network/u/stefanobaghino-da)\
**Post date:** [April 24, 2020, 11:20am UTC](https://forum.canton.network/t/command-deduplication-persistence/231/2 "2020-04-24T11:20:55Z")

</div>

Spot on, deduplication data is persisted on the sandbox, as well as any other DAML Ledger, to guarantee that command deduplication will continue working across restarts.