<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=332351) </details> <!--IssueSummary end--> Currently whenever we run GitLab Direct Transfer, for each entity (project/group) and for each of it's relations (issues/labels/pipelines/etc) we request relations export from Source instance and wait for export to complete before performing import. If said Source relations export for each relation is not completed when we check, we [`reenqueue`](https://gitlab.com/gitlab-org/gitlab/blob/c4b93aacf5e5759ac993b814f2f196964dbad47f/app/workers/bulk_imports/pipeline_worker.rb#L85-93) the job and re-try every 10 seconds. Since we have a lot of relation types this can produce bursts in network requests for source instance. Instead, we should re-try in a more exponential manner, increasing the wait time before checking if the export finished.