Since nodePrint refresh is now operating less frequently than it was initially designed for, I would suggest reviewing whether the maxAge should be increased or perhaps this chunk of code should be completely disabled.
Initially, the code was supposed to do a full refresh every month (30 days), and this forced cleanup would only happen on files that exceeded 100 days or three failed full refreshes. Under the current batch schedule, perhaps maxAge should be increased closer to six months.
https://github.com/LibreTexts/Libretext/blob/5ab710dec8291a5bdba5e613773748a0050ace46/nodePrint/nodePrint.js#L383-L387
Since nodePrint refresh is now operating less frequently than it was initially designed for, I would suggest reviewing whether the
maxAgeshould be increased or perhaps this chunk of code should be completely disabled.Initially, the code was supposed to do a full refresh every month (30 days), and this forced cleanup would only happen on files that exceeded
100 daysor three failed full refreshes. Under the current batch schedule, perhapsmaxAgeshould be increased closer to six months.