Comment 4 for bug 1609787

Well, you can disable cache, but it will be additional action. With that approach, user needs to know that if he wants to do actions A, he needs to do a list of actions B. If he doesn't he will be confused and looking for help. Even if he does not plan to recreate resource frequently he can stuck into this bug.
Safest way is to disable finder specific cache by default. But, that will make deployment slower, cache exists for a reason. And again, to make it faster, user needs to do additional actions.
So I think it is certainly better to resolve this automatically.