This is the original discussion about introducing the bot and my arguments for it: RFC: Introduce Stale-Bot on dev collections
For me, they are still valid 
We had a lot of PRs where the authors are pinged regularly by several release managers asking if the PR is still valid / worked on - without any response. As we are a polite community, no one dared to set a deadline or to close the PR.
So I thought it would help to set rules and have them neutrally enforced by a bot in order to concentrate on a smaller set of actively maintained PRs. IMHO, it would help the project to focus on a small set of PRs instead of having a lot open degenerating over time and never get merged.
There are some adjustment screws to tone down the bot, eg. tweak time frames or add tags to avoid the bot from doing anything. But I do not insist to keep it if you don’t find it helpful.