Skip to main content
Contributor I
February 25, 2026
Solved

Internal Alert Recipients Automatically Disabled

  • February 25, 2026
  • 3 replies
  • 129 views

We have two separate clients that are using internal alert flows where their individual emails keep getting automatically disabled from the recipient list. I am also a recipient on both flows and my email has never been disabled. One flow has been set up for about 7-8 months and the account owner’s email has been disabled at least 3 times, and the other client’s has been disabled once in the 3 months his flow has been set up. 

Each time I have to go into the flow and trigger (resend) the consent authorization for them which then reactivates their email, until it doesn’t work again at some point. Neither of them are actively unsubscribing from these notifications either, since the forms tied to the flows are imperative to their businesses. 

 

Any idea why their emails keep getting disabled? 

    Best answer by Kim from Cadence

    @Envision, very strange! I haven’t seen this before. If you haven’t already, I’d recommend filing a ticket with Klaviyo support to look into this. 

     

    Cadence / Book a demo

    3 replies

    Kim from Cadence
    Partner
    Partner
    February 26, 2026

    @Envision, very strange! I haven’t seen this before. If you haven’t already, I’d recommend filing a ticket with Klaviyo support to look into this. 

     

    Cadence / Book a demo

    Kim — Founder @ Cadence | Helping brands automate recurring campaigns (daily, weekly, monthly) | Happy to connect! | https://cadencecampaigns.com
    Byrne C
    Community Manager
    Community Manager
    February 26, 2026

    Hi ​@Envision,

    Welcome to the Klaviyo Community! If you’re certain that these internal alert recipients are not unsubscribing from these alerts, then them being auto-disabled isn’t expected. I’d recommend reaching out to Klaviyo.com/support, so our team can take a look into this to determine why this is happening!

    EnvisionAuthor
    Contributor I
    March 3, 2026

    Thank you for the responses. One client has already reached out and informed me that Klaviyo Support said they “ran a script” on the backend to prevent it from happening again. I’ll continue to monitor the other client’s deliverability and see if the issue pops up again.