I noticed that moveChunk commands initiated by a user are retried an indefinite amount for retriabale errors.

I don't think it's good practice to retry errors an infinite number of times, since if there is an actual underlying issue causing the error, despite it being "retryable", the command will appear to hang rather than surfacing the issue to the user. 

This ticket came out of this PR thread.