Unsubscribe to status.apigee.com

[#1]

I subscribed to status updates on support.apigee.com . But I cannot unsubscribe. In the status email, there is a link to unsubscribe

To manage your subscription: http://www.statuspage.io/manage/<code>;

but when I visit that page, I just get a generic statuspage.io page . I logged into statuspage.io with my email address that is subscribed to status.apigee.com but I don't see any way to manage my subscription

[mschreuder · Accepted solution]

Hi @David.Biesack@sas.com,

Seems you may have the wrong link to manage subscription. I'm not sure how that would have happened but the link you need is: https://status.apigee.com/manage/<code>;

Hopefully the same code you have will work and then you should see a page that looks like this:

I did also review the subscribers to Apigee status but I didn't find a match with the email address you are using in Apigee Community. If you message me the email address you used to subscribe I can unsubscribe you that way too.

If I have helped answer your question, please click the Accept link, or let us know how we can further assist.

[mschreuder]

Hi again @David.Biesack@sas.com I just tried a different method and I have been able to locate your subscription, please let me know if you would like me to unsubscribe you or if you would like try the method I described above?

[#4]

Thanks, mschreuder

The problem is in the Email that is sent for [Apogee status]. While the 'manage your subscription' link is correct in the HTML mail, the link in the text/plain portion of the email is incorrect:

--

Incident Status: http://stspg.io/2Ydh

Apigee Status: https://status.apigee.com

To manage your subscription: http://www.statuspage.io/manage/<code>;

(I replaced the actual code with "<code>" here.)

This should be https://status.apigee.com/manage/<code>;

Using the correct link, I can update my subscription. Apigee should fix the email template for the text/plain section.

[mschreuder]

Thanks @David.Biesack@sas.com for bring this to our attention. I have initiated follow-up to get that corrected. Hopefully we'll be able to resolve it soon and thanks again for letting us know about it.