Parameter:
AMgr_MaxRetriesShort description: Maximum number of retries with which the Agent Manager re-runs a failed agent before giving up.
Profile
Parameter | AMgr_MaxRetries |
Category | General |
Component | Server |
Available since | 10.0 |
Supported versions | 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | Server document (Server Tasks → Agent Manager) |
Possible values | Integer (default 2; typically 0–5) |
Description
If an agent is aborted due to transient issues (memory, lock, brief DB error), the Agent Manager attempts to restart it up to
AMgr_MaxRetries times. Once all attempts are exhausted, it writes an error entry to the log and, depending on configuration, marks the agent as disabled.Low values prevent endless retry loops; high values increase resilience.
Example configuration
AMgr_MaxRetries=3
Notes & pitfalls
- A value of 0 disables retries completely.
- Complements
DEBUG_AMGR,AMgr_DocUpdateEagerness.
- For very short-lived memory spikes, tuning server resources is more effective than increasing the retry count.
- Check logs in
log.nsf(Agent Manager entries) and the console.
- The change takes effect after a restart of the Agent Manager.