I’ll investigate the issue further. In the meantime, I would suggest removing the background image from your project and re-adding it with a new name. That should correct the issue.
I was recently having the problem with images getting uploaded to the website again. I turned off generate webp and all the images are exported and showing on the website now. Web browsers I tested Duck Duck Go, Safari and Chrome, all running the newest version on Tahoe and all reloaded the webpage with images without clearing the cache.
Just had the same problem with exporting. I renamed some of my images in the asset manager. After exporting my project these newly named images were missing.
I had problems with placed images and images used for backgrounds and images used in the background for a div and Masonry Collage. It was across the board, I tried putting the Asset Manager in manage mode and fixing some image sizes and setting the Always Export slider on, but nothing helped until I went into the Project Settings and unchecked Generate WebP. But I did do something else during that time and that was uncheck the Enable Image Protection Site Wide, don’t know if that was related but may give a clue.
I’m not sure if I can reproduce this problem, it seemed to happen when I imported some jpgs from a camera that had files names like IMG_xxxxxx.jpeg I did a rename of all the images to Ex: camping-trip-01.jpg and incremented the file name like 01, 02, 03 etc and of course changed the file extension from jpeg to jpg and it was some but not all of those images that had the problem. Blocs exported the jpg and the webp versions of the files and they were all there in the export “Command E” and then I checked the code in the page and the links to the images were there, but the images just would not show up on the page.
This is a real head scratcher, I will post back anything else that comes to light.
In my case, the issue affected Bloc background images. The image files were present on the server after publishing, but they were not being displayed on the page. Re-adding the image resolved the issue.