Low impact. If one market goes down or becomes unresponsive, users wont be able to retrieve their pending interests for any of the subsequent markets. This can lead to misinformation and might affect user decisions.
Take a look atgetPendingInterests():
As seen, theres a loop that goes through all available markets to fetch the boosted pending interests for a user. However, if any of these calls (like getInterestAccrued) fail due to market unavailability or any other issue, the loop will be interrupted.
To ensure the functions resilience and provide accurate information even if some markets are down, wrap the calls inside the loop in a try/catch block. If a call fails, log an event indicating the market that caused the failure:
By incorporating this change, even if a market fails, the loop wont break, and the function will continue to retrieve the pending interests for the remaining markets. The emitted event will notify off-chain systems or users about the problematic market.
