If there's a different code that skips that file and lets sync continue with other files, that's great.  If not, a 503 should be good until there's a client update specifically for this purpose, killing the current sync but then resuming when the file becomes unlocked (hopefully, usually) on the next pass.