When the custom clients feature is enabled, credentials use the secret ARN as their ID rather than the secret name.

However when a job attempts to bind a credential that uses the secret ARN as its ID, the binding fails with an error along the lines of "could not find credential with the ID '<ARN>'".

The same binding for the same credential works fine when the default client is used, so the credential uses the secret name instead.