Skip to main content

Today’s outage exposed a gap in our plan and processes when it comes to our community. We have a status page and processes for outages of our platform, but not anything specific to our community when DH is having a platform outage. 

Hopefully this is a plan that never needs to be used, but I think I need one. Questions I’m thinking through:

  • Length of outage - what’s the threshold for when you need to alert community members? 
  • Messaging Channels - Post on other webpages, if so which one? Email?
  • Follow up - at what point does this become something we should share a retrospective with community members?
  • Levels of action - how do tactics change as the length of outage grows?

Fortunately, most DH outages are very short and/or isolated to features, not platform wide. But what plans and best practices do you have? 

Good point @DannyPancratz  I was also thinking similar - we don’t have a custom error page set up which directs our members to other places.
My community doesn’t use the native GSDH Ideation and Product Update features (yet) so an outage has relatively low impact but something to keep in mind for future as my community grows.
Perhaps something that the GS team can give some steer on. I know this wasn’t discussed during onboard.

Reply


Terms & ConditionsCookie settings