We have observed that sometimes Jenkins does not pick up new secrets after they have been added to kubernetes.  

We do not observe any seemingly related errors in the jenkins log and are forced to restart jenkins in order for it to pick up the new secrets.

Sometimes it does find the new secrets but not always and there is not a clear indicator of when it will or will not find new secrets and display them in the credential store UI.

Is there any way to manually have it rescan for secrets?