Skip to main content
valerie_anders
Level 3
December 7, 2023
Solved

Adobe Launch dev url is giving a 404 error

We have been using Launch for years now.  Today we keep getting a 404 on our Dev environment link.  We have rebuilt the library and still get the problem.

 

Any ideas on what to try?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Jennifer_Dungan
Jennifer_DunganAccepted solution
Adobe Champion and Community Advisor
December 8, 2023

Right now, compiling is likely failing due to the major outage affecting most clients:

 

https://status.adobe.com/

 

Nothing like trying to troubleshoot your own issue with a larger system one in progress.....

View in thread

4 replies

abhinavbalooni
Community Advisor
abhinavbalooniCommunity Advisor
Community Advisor
December 7, 2023

Hey @valerie_anders 

Very similar issue here: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform-data/adobe-launch-embed-code-not-found-err-aborted-404/td-p/572355

 

See if the above helps?

 

Translate
Jennifer_Dungan
Adobe Champion and Community Advisor
Jennifer_DunganAdobe Champion and Community Advisor
Adobe Champion and Community Advisor
December 8, 2023

Unlike the other question that was posted where the Staging Environment had been bypassed in the Publishing Flow, the Dev environment cannot be bypassed.

 

However, here are a few things to check:

1. Make sure that the Dev Environment install code is the same as is configured on your website (Launch Property > Environment, Development > Install icon, check the Code against your environment.. 

 

2. Make sure your Publishing Flow actually has the Development environment selected... you can have multiple Dev environments, it's possible to save a library to any of your Dev environments, or to non-environment at all.. 

 

 

 

if those look correct, you could try removing the environment and saving your library, then selecting the Dev environment again and re-building... 

 

I had a similar experience a year or so ago with a Demo site I didn't work on often... I don't recall what ended up working in the end, but after a few rebuilds and double checks, I was able to get it to properly build and not 404...

Translate
ValerieAnders
Level 2
December 8, 2023

 

We switched between different dev environments yesterday.  Today one of the dev environments had a build date in October even though it was showing that the last modification had been yesterday. 

 

The other dev environment is showing this for a build date.

window._satellite=window._satellite||{},window._satellite.container={buildInfo:{minified:!0,buildDate:"2023-12-07T19:58:37Z",turbineBuildDate:"2023-02-22T20:37:26Z",turbineVersion:"27.5.0"

But has this for a last modified date: Dec 7, 2023, 3:46 PM

 

Today, I have done as you suggested and removed the environment completely and then reattached the dev environment that was showing an October date.  Now the code does not compile and the error is 'unknown'.  I am opening a ticket with Client Care.

Translate
Jennifer_Dungan
Adobe Champion and Community Advisor
Jennifer_DunganAdobe Champion and Community AdvisorAccepted solution
Adobe Champion and Community Advisor
December 8, 2023

Right now, compiling is likely failing due to the major outage affecting most clients:

 

https://status.adobe.com/

 

Nothing like trying to troubleshoot your own issue with a larger system one in progress.....

Translate
Terms & ConditionsAccessibility statement

Loading footer...