diff --git a/docs/guides/dao/dao-known-issues.md b/docs/guides/dao/dao-known-issues.md
index 04dce0ea9a..2c120045e5 100644
--- a/docs/guides/dao/dao-known-issues.md
+++ b/docs/guides/dao/dao-known-issues.md
@@ -32,3 +32,9 @@ An attacker can create spam proposals with the intent of locking DAO_CATs into v
 In the event that such proposals are voted on by users, because the proposals can never be closed (even via self-destruct), any users who voted on these proposals will never be able to unlock the coins they voted with. Note that coins in this state could continue to be used to vote on other proposals.
 
 The current mitigation to this is that the wallet will filter out any proposals which either don't meet the proposal minimum amount or don't have valid timer coins. It is strongly suggested to use the `show_proposal` command with any proposal that you intend to vote on, and check that it is valid.
+
+## Resync with locked DAO CATs
+
+This issue occurs when you have a balance of locked DAO CATs which have voted on one or more open proposals, then you delete and resync the wallet DB. Once the proposals have closed, attempting to unlock the coins from voting mode will fail due to missing lineage proofs for the locked coins.
+
+Mitigation: This issue only exists in the 2.1.2 release. It has already been fixed in the `main` branch. To release the coins, launch the wallet from `main`, and then run the [release_coins](/dao-cli#release_coins) command.