You have a scheduled agent that runs at a set frequency (such as 30 minutes). This schedule agent runs correctly most of the time. If, however, the agent attempts to execute (per its schedule) while Compact is running on the same database, the agent stops running. The agent is also removed from the scheduled queue. (The scheduled agent queue is an internal queue that keeps track of which agents need to run.) The agent is not returned to the queue until Agent Manager refreshes the Cache. By default, the Cache is refreshed at 12 a.m.
Starting with Domino 8.5.2 Fix Pack 3 and 8.5.3, you can use the following parameter to force agent retry despite the Compact:
DEBUG_AMGR_ENABLE_RETRY_ON_COMPACT=1 Workaround for earlier releases The following provides additional technical details on the expected behavior: To determine if the flag has been set for a database you can use the following parameter in the Domino server’s notes.ini: debug_amgr=l (lowercase L) The following will appear in the log: “AmgrDbg: CheckDbForTask – Setting DBOPTION_NO_BGAGENT for database When the flag has been cleared by the Cache refresh or Fixup the following entry should be observed: “AmgrDbg: CheckDbForTask – Clearing DBOPTION_NO_BGAGENT for database |
The information above is from TN 1084223