 Steven says, what's the best way to send out an automated email each month to a client? I have posted this before and did it with Flow, but that seems to be gone and my prior Flow automations don't work any longer. Interesting scenario that Flows are disappearing and don't work anymore when they once did. It makes you wonder if the Flow was accidentally deleted or maybe shared with another user. And when you share a Flow with another user it's kind of removed from your initial landing page within Power Automate and it goes into, I think it's called the shared tab. And it could also be not working because of things like password changes to the account that you're tied to the action or the connection, I should say, within the Flux. Yeah, so it could lose its context. So that might explain why it's broken. Why it goes missing? I don't know. But I do like the idea of using Flow to build out your customer emailer. What does everyone else think? I agree. I mean, direct link that I threw in there, send an email on a schedule. They've got a nice template for it. Two things to remember with Flow. One, whoever makes the Flow originally that's the license that it's tied to. So first of all, if that person leaves the company and that account is deactivated and the Flow is not beneficially shared or reassigned to another account then that can end the Flow will stop working. In addition, this also could be a licensing issue. So whatever account they use to set up the Flow if that license has been disabled or didn't get renewed or there's an issue with it it'll make it appear like Flow is not working even though it is. But that particularly licensed piece isn't making anything happen. Those are the only things I can think about. I agree Flow's the best way to handle it but it sounds like there's probably some identity or licensing issue that could be causing it to look like it's broken. Yeah, the point you raise Sharon this brings us back to the days of creating service accounts to run things in. And though you can't exactly power automate, you can designate users and users you wanna run Flow's within and treat them specially. Think about old SQL DTS packages or Windows services and those sorts of things. We always recommend to every client that's going to be using Power Automate for enterprise processes of any sort to create a service account and tie all of their Flow's initially to that service account or at least share them with the service account if it's gonna be a personal Flow and understand that the personal Flow's could potentially die when the person leaves and that's just how it is. That's been a problem since day one and the expert advice out there has been service accounts around that. You run into that with every client? Yes, in fact, we also recommend that whatever service account they use for all those Flow's that that's the one that they tie the power, we get a power apps license for that particular account because then it covers unlimited Flow's and the power apps that they're gonna be building with the service account as opposed to worrying about the users because users can only create a certain amount of Flow's per license but if you get the power apps monthly and assign it to the service account, it essentially, I'm not gonna call it a hack but it's a creative workaround.