API call to file history returns 500 if the file was renamed/moved (BBCC-1111)

After the file was added to the repository, if it was renamed or moved after a couple of commits, when making an API call to the file history returns
500 Internal Server Error
{
"type": "error",
"error":

{ "message": "Something went wrong",}

One workaround that can be used is to make the same call to the file history with
?renames=false
that will return the SHA commits where the file had changed but it will not return any commits past rename