https://github.com/code-423n4/2024-05-predy/blob/a9246db5f874a91fb71c296aac6a66902289306a/src/libraries/logic/LiquidationLogic.sol#L39-L119
This function is used to liquidate a vault that is now in danger as the name suggests and it takes in several parameters, including the vault ID, a close ratio, global data, and settlement data. The issue, however, as hinted with the @audit tag is with the integration of the _MAX_ACCEPTABLE_SQRT_PRICE_RANGE which is hardcoded as 3%; in a case where this attempt at liquidating validly pushes the price above this limit the transaction erroneously reverts when checking the slippage
Borderline medium/low, since this leads to a DOS to liquidations in turbulent situations, which then hints how protocol are allowing themselves more risks.
Consider not hardcoding this value so its settable depending on the current market situation.
