Overview
If an automatically calculated or concatenated property is used in the PDF Processor and that property is changed or updated and the Recalculate is run, it can end up with the PDF Processor module checking out *all* documents with this property being inserted/stamped into them. This can cause the system to become unusable as thousands of documents can be checked out as the PDF Processor works through them.
This can also interfere with other automatic processes such as workflows, event handlers, applications, and more as the system has checked out thousands of documents.
The PDF Processor has a "Maximum Polling Interval in Seconds" that defaults to 30 seconds. This means it will process about 2 PDFs per minute. This could mean that documents are checked out for days or weeks at a time.
Solution
If such a situation occurs, the process can be sped up by setting the "Maximum Polling Interval in Seconds" = 0.
NOTE: This should only be done in "system unusable" cases. The PDF Processor module is very CPU and RAM intensive most times. If this setting is left at 0, this could cause max CPU consumption which could cause instability, locking/jamming, or other undesirable effects on production systems.
