A protected var not exposed to CI for protected branch

Summary

Protected env not always exists during pipeline execution

Steps to reproduce

  • Define protected variable
  • Make protected branch
  • Put export to pipeline
  • Run CI

2019-02-15_14-50

Doesn't exist: 2019-02-15_14-51

Press retry: 2019-02-15_14-51_1

What is the current bug behavior?

Sometimes there is no "protected var"

What is the expected correct behavior?

Protected var must always exists

Results of GitLab environment info

Expand for output related to GitLab environment info 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info)
System information
System:
Proxy:		no
Current User:	git
Using RVM:	no
Ruby Version:	2.5.3p105
Gem Version:	2.7.6
Bundler Version:1.16.6
Rake Version:	12.3.2
Redis Version:	3.2.12
Git Version:	2.18.1
Sidekiq Version:5.2.3
Go Version:	unknown


GitLab information
Version:	11.7.3-ee
Revision:	d573592
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
DB Version:	9.6.11
URL:		https://gitlab.sipay.ru
HTTP Clone URL:	https://gitlab.sipay.ru/some-group/some-project.git
SSH Clone URL:	git@gitlab.sipay.ru:some-group/some-project.git
Elasticsearch:	no
Geo:		no
Using LDAP:	no
Using Omniauth:	yes
Omniauth Providers:


GitLab Shell
Version:	8.4.4
Repository storage paths:
  • default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git

GitLab Enterprise Edition 11.7.3-ee