"Destination returned error, status = 500" error message when requesting clone despite providing correct credentials for a user with the 'admin' roleIssue When requesting a clone, customers may get a "status = 500" error. This is an unspecified failure message, usually indicating authentication failure in the context of clone request. However, a customer may report it is possible to get this error while providing valid credentials for a user with the admin role when making the request.CauseCheck the admin role record for the "Elevated privilege" setting. If it is set to true, then users have to elevate to make the admin role active. This causes an issue when requesting clones because even though the role is assigned, it's not active until elevating, and no auto-elevation occurs during the clone request process, which causes an authentication failure. See the documentation on Elevated privilege roles: By default, you do not have elevated privilege roles upon login. You must manually elevate to the privilege of the role. An elevated privilege role lasts only for the duration of your user session. Session timeout or logout removes the role. . . The use of elevated privilege on the admin role is not supported and may cause unexpected behavior. To require administrators to manually elevate, see Force administrators to manually elevate.ResolutionAsk the customer to remove the "Elevated privilege" setting from the admin role and request the clone again.