Problem Statement
When a migrator initiates replication or materialization in Liberty — whether accidentally, with incorrect parameters, or against the wrong source — there is no way to cancel or pause the operation from the interface. The only recourse is to escalate to the Liberty/JCMA engineering team to manually terminate the backend job. This creates:

• Unnecessary support load — MSEs and CMMs must file escalations for what should be a self-serve action
• Wasted compute and time — Jobs run to completion even when the output is known to be unusable (e.g., wrong DB selected, test kicked off by mistake)
• Customer frustration — Migrator see a running job with no way to intervene, eroding confidence in the migration tooling
• Delayed migrations — Teams must wait for a failed or unwanted job to finish (or for engineering to kill it) before re-initiating with correct settings

Proposed Solution
Add Pause and Terminate/Cancel buttons to the Liberty UI for both:

1. Step 2 — Copy your data (Replication)
2. Step 3 — Load data into migration environment (Materialization)

Impact & Value

• Reduces migrator escalation volume — Self-serve cancel eliminates a recurring category of engineering escalations
• Improves migration throughput — Faster recovery from accidental or misconfigured runs
• Improves customer experience — Gives customers visible control over long-running operations
• Aligns with tooling maturity goals — Standard UX expectation for any long-running async operation