I’ve been having an issue for some weeks now trying to land some minor changes to one of my projects. Most elements will land and update just fine, but the body.html is stubbornly refusing to make any changes stick, and I perpetually have a ‘1 change’ notification under the Land button.
The project runs fine in the preview with the html changes, and I’ve attempted to land the changes in question on several different machines and browsers.
Is there possibly something I’m missing here?
Hi, welcome to the forums!
Are you seeing an errors in the console or anything like that? Are you seeing the same behavior if you try from a different browser or clear your cache and cookies? Typically when there’s issues with source control like this it comes from some weird state the browser is in.
Hiya George,
Clearing cache and cookies hasn’t sorted it, unfortunately. Tried in multiple browsers too, with no change in result.
There is one error sometimes coming up during a landing build from:
/var/task/node_modules/extract-loader/lib/extractLoader.js
but it seems to be pointing to the tmp/src version of the body.html (that I’m trying to replace)
Anything else I can try here?
Can you share a screenshot of your project? I’ve never seen an error like that before.
For sure - but I should also mention that the landing issue predates this error. I’ve only seen this error since I attempted removing some unused assets in an attempt to troubleshoot the landing issue itself fwiw
From the error I’m gathering that you cloned the video sample project. Are you able to manually move your changes to a new project to see if you still face the same error?
I did indeed 
And yes, yesterday I did precisely that after some weighing up of options. Cloning the project allowed me to both land the changes I needed to as well as making this particular error disappear.
I was apprehensive to do this because public facing media had already gone to print, but luckily we use a redirect for precisely these kinds of unforeseen situations.
For future reference, is there any way to resolve this type of landing roadblock?
I’ve forwarded this to the engineering team so they can look into it. Thanks for the update!
