[BUG] salt minion 3002.2 keep old mine after mine.update

Description of Issue

After upgrade to 3002.2 from 2019 I have issue with old mine data at some minions.
If i run mine.update on salt-master on dubg mode I can see correct data sent to minion.
But mine.get returns still the old ones. Restart of salt-minion loads new mine data.

Setup

(Please provide relevant configs and/or SLS files (Be sure to remove sensitive info).)
Plillar for minion at salt-master
mine_functions:
network.ip_addrs:
cidr: x.x.x.x/32
test.echo:
text: 1613747101

text is regularly changing timestamp

/etc/salt/minion.d/_schedule.conf
schedule:
__mine_interval: {enabled: true, function: mine.update, jid_include: true, maxrunning: 2,
minutes: 60, return_job: false, run_on_start: true}

Steps to Reproduce Issue

(Include debug logs if possible and relevant.)

Versions Report

(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)

After removed salt repo for 2019 version we upgraded all minions to 3002.2

Salt Version:
Salt: 3002.2

Dependency Versions:
cffi: 1.14.2
cherrypy: Not Installed
dateutil: 2.7.3
docker-py: Not Installed
gitdb: 2.0.5
gitpython: 2.1.11
Jinja2: 2.10
libgit2: Not Installed
M2Crypto: Not Installed
Mako: Not Installed
msgpack: 0.5.6
msgpack-pure: Not Installed
mysql-python: Not Installed
pycparser: 2.20
pycrypto: 2.6.1
pycryptodome: 3.6.1
pygit2: Not Installed
Python: 3.7.3 (default, Jul 25 2020, 13:03:44)
python-gnupg: Not Installed
PyYAML: 3.13
PyZMQ: 17.1.2
smmap: 2.0.5
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.1

System Versions:
dist: debian 10 buster
locale: UTF-8
machine: x86_64
release: 4.19.0-14-amd64
system: Linux
version: Debian GNU/Linux 10 buster

Start by reviewing the mine_functions pillar and /etc/salt/minion.d/_schedule.conf, then reproduce the sequence with mine.update followed by mine.get on Salt 3002.2. Done means mine.get returns the current mine data without restarting salt-minion; no specific test or source file is identified in the issue.