<!--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> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=549583) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=549583) </details> <!--IssueSummary end--> ## Current Behavior - Bitbucket Cloud and Server **stage** workers have a default maximum interruption limit of 3 - Jobs get placed in dead queue after reaching the interruption limit - Migration status only changes to `failed` after 24 hours via `Gitlab::Import::StuckImportJob` ## Problem When Bitbucket import jobs are interrupted multiple times, they are moved to the dead queue even though they could eventually complete successfully. Additionally, users must wait 24 hours before seeing the failed status. ## Proposed Solution 1. Increase the maximum interruption limit for Bitbucket Cloud and Server workers (similar to [GitHub Import](https://gitlab.com/gitlab-org/gitlab/-/blob/2e8babc771fd88d05334a9001d36e40aa86e0bd9/app/workers/concerns/gitlab/github_import/stage_methods.rb#L44-46)) 2. Implement `sidekiq_interruptions_exhausted` callback in the jobs to mark migration status as failed immediately when the max interruption limit is reached. ## Expected Outcome - Fewer jobs will end up in the dead queue - Users will receive immediate feedback when imports fail due to exhausted interruptions - Better overall import reliability for Bitbucket repositories