Adobe Launch File throwing errors on buy flow but not homepage

[JanisGr]

We are currently switching from legacy DETM implementation of data collection. When testing our property using adobe debugger, we have the property fully loaded and no errors on the home page, but as soon as we click into buyflow we get errors thrown in the "launch-environment-id.js" file. Specifically when the launch file is trying to perform a split function on the environment variables. when i fetch the environment manually on console "development" is shown, which is correct, but what could be the issue that would cause the "e" variable in the build file to be undefined? Thanks in advance!

[RiteshY18 · Accepted solution]

@JanisGr  suggest to look into 

• The script may be referencing an incorrect or non-existent environment ID.
• browser may block the script due to CORS policy violations
  • Network tab and filter by JavaScript or search for the launch-environment-id.js file.
  • HTTP status code (e.g., 404 for not found, 403 for forbidden).

[bjoern__koth]

Hi @JanisGr 

The launch-environment-id.js script is not really a part of Launch.

How are you testing it? Are you injecting the Launch script through the experience platform debugger side by side with DTM?

[kautuk_sahni]

@JanisGr Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!