Issue Summary

This is a parent ticket tracking resiliency issues observed in the Link Migration Service (LMS) during link fixing jobs. These issues manifest as STATUS: Failed in the job

INTERNAL_ERROR failures, UPDATE_FAILED outcomes, and unexpectedly error out, resulting in incomplete link remediation post-migration. Any STATUS: Failed can be linked to this MIG

error: INTERNAL_ERROR description: "We couldn't complete this task" details: "This might be caused by a connection issue or problems on our side. Try updating the links again or contact Atlassian support."

Link any MOVE issues that result in a STATUS: Failed to this parent MIG so we can quantify these resiliency errors. This MIG should not be used for unhandled LMS patterns, those should be dedicated MIGs

Steps to Reproduce

1. Run a link fixing job via LMS

1. Wait for the job to complete and review the job result JSON

Expected Results

All links referencing the legacy source URL should be successfully identified and rewritten to the destination URL across all content areas (comments, issue descriptions, custom fields) with zero INTERNAL_ERROR or UPDATE_FAILED outcomes.

Actual Results

LMS jobs complete with INTERNAL_ERROR failures and UPDATE_FAILED outcomes across multiple link types and content areas. Affected link types include JIRA_BROWSE, JIRA_SERVICE_DESK, and JIRA_SECURE. Links are left pointing to the legacy source URL, requiring manual follow-up or job re-runs.

Workaround

Re-run the LMS link fixing job. In some cases this will result in a successful job