Edit repo mirror detailsdocs/repo-mirrors-and-sidekiq

1 files changed, 8 insertions, 10 deletions

diff --git a/doc/workflow/repository_mirroring.md b/doc/workflow/repository_mirroring.md
index a599eb0557d..9fcadbf3bee 100644
--- a/doc/workflow/repository_mirroring.md
+++ b/doc/workflow/repository_mirroring.md
@@ -138,20 +138,18 @@ upstream and GitLab will no longer automatically update this branch to prevent a
 
 ### How it works
 
-Once you activate the pull mirroring feature, the mirror will be inserted into a Sidekiq queue.
+Once the pull mirroring feature has been enabled for a repository, the repository is added to a queue.
 
-Sidekiq will:
+Once per minute, a Sidekiq cron job schedules repository mirrors to update, based on:
 
-- Start every minute to process the queue.
-- Schedule a fixed number of mirrors for update, based on the capacity available to Sidekiq.
+- The capacity available. This is determined by Sidekiq settings. For GitLab.com, see [GitLab.com Sidekiq settings](../user/gitlab_com/index.md#sidekiq).
+- The number of repository mirrors already in the queue that are due to be updated. Being due depends on when the repository mirror was last updated and how many times it's been retried.
 
-For GitLab.com, see [GitLab.com Sidekiq settings](../user/gitlab_com/index.md#sidekiq).
+Repository mirrors are updated as Sidekiq becomes available to process them. If the process of updating the repository mirror:
 
-If the mirror:
-
-- Updates successfully, it will be enqueued once again with a small backoff period.
-- Fails (for example, a branch diverged from upstream), the project's backoff period is
-  increased each time it fails, up to a maximum amount of time.
+- Succeeds, an update will be enqueued again with at least a 30 minute wait.
+- Fails (for example, a branch diverged from upstream), it will be attempted again later. Mirrors can fail
+  up to 14 times before they will not be enqueued for update again.
 
 ### SSH authentication