So I was working on, this particular, solution where I figured out I'd share this with the community, not specifically this workflow, but the concept remains the same across the board. So, I'll give you an example. So basically, this workflow is segmenting tickets based on their resolution to positive resolutions or negative resolutions. So what, what I'm doing is I'm making this scalable.

So how do you do that? For example, we have, you know, bunch of resolutions, like, you know, discount applied, unresolved churn, or whatever. But let's say someone adds a new value in that same property. Now it goes to the workflow, and it will go through the the Nunberg branch and nothing will happen.

So what do you do? You set an internal notification. Ticket resolution was not categorized. Please check if there is a new resolution value added to the resolution property on the ticket object.

Please update this automation to reflect the same and enroll the tickets so the data is correct. So what I'm saying is, hey. You guys added a new value or someone added a new value in the property. Ideally, there should be, you know, one CRM or two CRM product owners or more based on the size of your organization.

But, you know, it's not perfect world. Someone might still, you know, add new values and stuff. So when that happens, your workflows should capture these nonmet conditions. And, you know, you'll send your notification to yourself, your manager.

In this case, I've, added Brian, who's my direct manager. So that we are aware, okay, this happened and then we can, you know, fix that. And if you don't do that, the result is a lot of tickets will end up not being categorized, which will have a lot of downstream effect on the last solution that we're building. Out.

So, yeah, I just wanted to share this. Hopefully, it's, a value for someone. Thank you.