Release Notes › Known Issues › Endpoint Types › General › Endpoints with Retry Autolock must be Configured with a Generous Retry Limit

Previous Topic: General

Next Topic: Account Templates are not Synchronized with Accounts on a Create or Modify Task in the User Console
Endpoints with Retry Autolock must be Configured with a Generous Retry Limit

For endpoints that have "N" retry autolock” behavior, the account used to connect to the endpoint using Java CS should be configured to have a generous (or unlimited) “N” due to attempts to connect being used up quickly by the Java CS.

When the account is natively locked due to "N" being exceeded, it may be necessary to use native tools to unlock the account before the endpoint can be acquired again. This depends on the exact native "locked" behavior of the endpoint.