So as a product is currently in production also, so there are sometimes, you know, some product issues come in which we had not thought of when doing the requirement implementation time. So when such scenario comes, we try to handle why that you know, why that what was the steps that that issue occurred. So we try to identify the steps. Was that a valid use case, you know, whether that steps were correct or was that an invalid steps that user has taken. If it is a valid step, how many users are impacted by that bug, how many, how frequently that bug would come. And based on that, the priority of the bug is decided that if it is something, you know, every user would face. Let's say if there are 10,000 users, the 5,000 are facing that that's a high priority bug and we try to resolve it as soon as possible, trying to understand the requirement on how to handle it. But if it's something that came up during, you know, an edge case scenario, then based on the priority being an edge case, we might ignore it if it's not that of a priority and not that of a simple step. Also, the businesses always require involved in such decisions.

