### Summary It seems that when removing a cluster there is a small window where the cluster has been destroyed but the associated applications have not. If a call to the `cluster_status` endpoint is in progress while this happens, an error is raised: * https://sentry.gitlab.net/gitlab/gitlabcom/issues/867068/ * https://sentry.gitlab.net/gitlab/gitlabcom/issues/851151/ Low impact as I don't think this is actually visible to the user (as the cluster has already been removed). ### What is the current *bug* behavior? `cluster_status` endpoint raises `undefined method application_jupyter for nil:NilClass` ### What is the expected *correct* behavior? `cluster_status` endpoint returns without error ### Output of checks This bug happens on GitLab.com ### Possible fixes