Geo: Project sync failures usually double-increment `*_retry_count`
Project sync failures usually double-increment
*_retry_count. Not a huge deal, but inaccurate and unexpected.
- We rescue certain exceptions in
update_registry!start call earlier to guarantee that it has been called by the time
fail_registry!can be called
Remove increment from
- Ensure in-progress syncs are not counted as failed (I think this bug was introduced while fixing this problem a long time ago)