Latest library build not updating | Community
Skip to main content
C
CelinaBe
Level 1
March 9, 2026
Solved

Latest library build not updating

  • March 9, 2026
  • 1 reply
  • 21 views

Hi, I have published a new build for a staging library on Adobe Data Collection, but when I try an debug it I see that a build from last week continues to be loaded. I unpublished it, republished, updated all of the versions and nothing.

 

What are the common explanations for this? Is there anything that we can do maybe on the hosting of the stage environment for example to fix it?

Best answer by Jennifer_Dungan

Are your Launch files using https://assets.adobedtm.com/ ? Or is a different domain being used?

As far as I am aware, the default “adobedtm” domain doesn’t have any cache (at last for development and staging files). There is probably some cache for prod that is cleared as part of the “push to prod” step.. I use self-hosting for prod in my setup, so we have to deal with our own “caching” which is part of our Jenkins job for deploying the self-hosted SFTP in Launch to our site.

 

What you are describing sure sounds like a cache issue, and if you are using self-hosting, then that is likely the case.

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
March 9, 2026

Hi, 

 

Just checking a few things:

  1. You are sure you built your “staging” file, you didn’t just sent it to be “approved”? You are sure you didn’t by pass Staging, and Deploy to Production?
  2. Are you using self-hosting or Adobe’s hosting?
    • If using self-hosting, are all your internal jobs and cache clear working properly?
  3. You are sure that the library built correctly (didn’t error out)?

 

I assume you are looking on your site and checking the build date to confirm which version is loading on your site? And you aren’t using anything to locally override the file?

C
CelinaBeAuthor
Level 1
March 11, 2026

Hi Jennifer,

Thank you for getting back to me.

I found a few new things for my investigation:

  1. I am indeed building libraries into staging or dev so that I can guarantee
  2. What I noticed is that today, the version of the library available on staging has been updated to a version I published on Monday. This means that there’s a severe delay of three days.
  3. I thought that maybe if I tried injecting the dev library in the staging environment, I could force the update, but this hasn’t been successful. However, I do notice that when I do that the version that is injected is the same old build, not the new one. So the injecting is successful but not the update.

 

Based on these tests, I am suspecting that the issue is in the communication between Adobe and the website maybe? It was suggested to me that the staging and dev environments might have a caching system that blocks the JavaScript from running as well.

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
March 11, 2026

Are your Launch files using https://assets.adobedtm.com/ ? Or is a different domain being used?

As far as I am aware, the default “adobedtm” domain doesn’t have any cache (at last for development and staging files). There is probably some cache for prod that is cleared as part of the “push to prod” step.. I use self-hosting for prod in my setup, so we have to deal with our own “caching” which is part of our Jenkins job for deploying the self-hosted SFTP in Launch to our site.

 

What you are describing sure sounds like a cache issue, and if you are using self-hosting, then that is likely the case.

Terms & ConditionsAccessibility statement

Loading footer...