Custom probot instance doesn't pick up repositories after stale.yml is added

Hi, First of all, thanks for the nice tool!

I run a custom Probot-stale instance with GitHub Enterprise. When I add it for an organization Probot schedules all repos (Scheduling interval in logs) and then de-schedules those where the stale.yml files are not found (Canceling interval).

The problem appears when I add stale.yml config to a repo after it has already been de-scheduled - it never gets scheduled again until I restart the Probot (tried to wait for 3 days).

In the logs I can see that Probot detects that the config file is there:

GitHub request: GET /repos/:owner/:repo/contents/:path - 200 OK
params: {
"owner": "my_org",
"repo": "testrepo",
"path": ".github/stale.yml",
...

nevertheless the Scheduling interval line never appears again and existing issues don’t get marked.

Please advise.

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.92. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[cyberhck]

Noooo