You can't get your money out of the vault, not because the vault is insolvent, but because you're at the back of the withdrawal queue, and the high-risk market ahead of you doesn't have enough assets to pay out your redemption right now.
The vault spreads everyone's funds across several lending markets. When you request a withdrawal, Morpho Vault V2 processes it by first using idle funds, then withdrawing from the single market that the current liquidity adapter points to. If that market has fully lent out all its funds (100% utilization), and the vault's idle funds are also exhausted, any withdrawal request will simply fail.
If you're lined up behind a high-risk market that has run out of liquidity, you'll have to wait for borrowers in that market to repay, or for the vault administrator to reallocate liquidity to other pools, before you can get your money.
Step 1: Identify the 'Number One' Market in the Current Withdrawal Queue
Figure out which market the vault is now relying on to provide withdrawal liquidity. Use Morpho's official documentation or on-chain query tools to find the vault's currently configured liquidityAdapter address and the corresponding liquidityData. In V2, all withdrawals are processed from the single market pointed to by the unique 'liquidity adapter' — there's no iterable exit queue as in V1. This helps you pinpoint the single market blocking your withdrawal.
Step 2: Check That Market's Utilization and Available Liquidity
See if all the money in this market has been borrowed out. Use the Morpho GraphQL API or a block explorer to query the market's utilization and current available liquidity. If utilization is near 100% and the vault's idle funds are zero, your withdrawal request will inevitably fail, confirming that the market doesn't have enough cash to pay you right now.
Case A: The Market Is Only Temporarily Drained, but Still Operating Normally
Wait for borrowers to repay or for the administrator to execute reallocate. The forceDeallocate mechanism lets anyone trigger a liquidity reallocation; if its fee is set to 0, you could try triggering it yourself, though it may also be exploited maliciously.
Case B: The Market Has Malfunctioned or Suffered Severe Risk (Bad Debt / Price Depeg)
The curator will immediately set the supply cap to 0, halting new deposits. Then, after the timelock period ends, they will forcibly remove that market from the withdrawal queue.
Risk Notice
If the vault version is V1.0, forcibly removing a market causes bad debt to be immediately shared proportionally among all depositors—your position's net value will shrink instantly. If it's V1.1, the bad debt loss won't be socialized across everyone right away; instead, the last batch of withdrawing users will bear the entire loss, making it impossible to withdraw your funds.
Common Causes of Withdrawal Failure
Many people think that DeFi vault withdrawals are like demand deposits that can be taken out at any time. In reality, the settlement cycle of the vault's underlying assets is limited by the loan repayment speed in markets. For example, during the Altura vault incident, a collapse in market confidence triggered a bank run with 8.5 million USDT flowing out in a single day. Users discovered that the repayment cycles of different assets simply couldn't match instantaneous withdrawal demand. Once withdrawal requests exceed the vault's available instant liquidity, a queue becomes unavoidable.
Next Steps
If you find your withdrawal is stuck, the first step is to determine whether you're dealing with Case A or Case B. If it's just temporary illiquidity and the forceDeallocatePenalty is set to 0, you could try calling the forceDeallocate function yourself to pull liquidity back into the vault and then resubmit your withdrawal. If a high-risk market has imploded, pay close attention to curator announcements and the vault's timelock proposals. Before bad debt is socialized, evaluate whether to exit immediately at a discount or hold on and bear potential losses while waiting for recovery.
