## Summary Currently our pipeline authoring apps use polling to fetch the status of pipelines every n seconds. With GraphQL subscriptions, we can establish a socket connection and have the pipeline data auto-push from the server to the client side when updates occur. Our infrastructure as a whole has support for this and [other teams](https://gitlab.com/groups/gitlab-org/-/epics/1812) have been leveraging this approach. We need to look into what specific updates are valuable to use subscriptions, but a few that are top-of-mind would be - Pipeline creation - Pipeline status - pipeline mini graph - pipeline graph In order to use subscriptions, we need to set up our architecture to do so. - [GitLab documentation on real-time updates/subscriptions](https://docs.gitlab.com/ee/development/real_time.html) ## Data analysis to support this prioritization