Expand my Community achievements bar.

SOLVED

Adobe Launch embed code not found (ERR_ABORTED 404)

Avatar

Level 5

Hello everyone!

In our website, we used to use the same environment (development script) for both our development and quality websites, both using the same report suite. However, we are trying to fix some errors and decided to correct that. Therefore, we kept the quality website with the development script since we did not want to lose the data and previous tests, and in the dev website, we replaced the development script for the staging. 
Thus:
development website: staging script

quality website: development script

production website: production script

With that, we created a new report (copying the evars and setups from the suite), inserted it in the adobe analytics launch extension, and published everything (flow) to the production.

However, we are getting this error:

fern1_0-1675849070161.pngfern1_1-1675849154930.png

 


and the link is as not found.
What could be happening?

1 Accepted Solution

Avatar

Correct answer by
Level 5

We found the error with the help of the technical team.

the problem is that nothing was published in the staging environment, we were publishing for production approval.
once we build it to development and then staging and left it there, it worked! 
But now we also correct the codes and switched development to the correct website. 

Thank you Jen!

View solution in original post

4 Replies

Avatar

Community Advisor

You could try the publishing again to be safe? Making sure that staging is properly built and deployed during the flow?

 

Also, can you check that your Staging environment is set to use Adobe as the host?

 

Jennifer_Dungan_0-1675878789495.png

 

If you are using self-hosting, then pointing to the assets.adobedtm.com domain wouldn't work.. you would need to point to the correct location.

Avatar

Correct answer by
Level 5

We found the error with the help of the technical team.

the problem is that nothing was published in the staging environment, we were publishing for production approval.
once we build it to development and then staging and left it there, it worked! 
But now we also correct the codes and switched development to the correct website. 

Thank you Jen!