What to change AFTER import and BEFORE activation: connections, lookups, schedules, certificates. SKIPPING ONE IS HOW TEST WRITES TO PRODUCTION.
The window between import and activation is the whole of this lesson. Before activation the integration exists and does nothing; after it, it runs against whatever it is pointed at. Every correction belongs inside that window, and the order is not negotiable.
CONNECTIONS FIRST, AND VERIFY EACH ONE INDIVIDUALLY. Endpoint correct for this environment, credential supplied, test connection passing. This is the item that causes the failure in the title: a connection carrying a source-environment endpoint means the promoted flow reaches back into the environment it came from.
LOOKUPS SECOND. Present, and carrying THIS environment's values — which is a different check from "present", because an imported lookup arrives complete and full of test codes.
CERTIFICATES THIRD. Uploaded in this instance, and not expired. They do not travel, and their absence reads as a network fault.
SCHEDULES LAST, BECAUSE ACTIVATING IS THE IRREVERSIBLE STEP. Everything above must be right before anything is allowed to run — and the schedule is what allows it.
THE CHECKLIST IS WRITTEN DOWN AND TICKED, NOT REMEMBERED. Promotion happens under time pressure, late, by somebody who has done it many times, and that is exactly the condition under which one item is skipped because it was fine last time. The failure mode is not ignorance, it is familiarity.
AND THE FINAL ITEM IS A POSITIVE PROOF RATHER THAN AN ABSENCE OF ERRORS: run one record and confirm it landed in THIS environment's target system. A flow that silently reaches the wrong environment does not fail — it succeeds, in the wrong place, which is why "no errors" cannot be the last check.