Why does a Reclamation rule only run once?

[Kenneth Galant1]

I have understood that each time a Reclamation Rule is triggered, that user would get an email for Low Usage. i.e Rule is need to use Acrobat once a month, if not Reclamation Candidate created.
What ServiceNow looks to be doing is you can only have 1 Candidate created for that product for that installation. EX: If Rule is triggered again. ie. last month I did not use Acrobat. I still needed it, it was approved, Candidate closed. 2 months later I still did not use Acrobat again, Reclamation Candidate will NOT be created. ServiceNow says 'Removal Candidate for [Product] already exists. Even though original Candidate is Closed. Meaning ServiceNow does not continually manage Low Usage SW. It appears to do  it just once per CI per product with a Reclamation Rule. It appears to assume once you get approval to continue to use, regardless if you never use it again, you get to keep the allocation. Tried in multiple instances. 

[Daniel Slocum]

Hi Kenneth,

I think you raise a valid point.  I've shared it with our Product Management team. 

Brainstorming a solution for you...  I would look at creation of a job to clean out Closed Reclamation Candidate records.  Just be careful to not remove those that have closed because software was uninstalled. Those are used for savings calculations on dashboards. 

[EdanR]

Hi Daniel and team,

I am kindly requesting more extensive documentation regarding on the following

1. triggering of reclamation rules and their associated notifications; when or when isn't retriggering executed. If retriggering is not possible out of the box, how it can be configured.

2. How manager approval assignment is handled. and how the manual uninstallation of removal candidates is handled with tasks and/or automation.