Is it possible to have this just be a flip of a switch globally?

Or there is something else going on with my cases. But you reacted before if your project did not change. But then it makes sense for cache to work, but i have this issue even when making changes. I just don't understand it. The only way to work around this is to delete the whole service and create a new one (and even worse i have to choose a different name for the new service). Only then i don't have caching issues. It's so annoying when you are trying to test a deployment before deploying on production.

you can just clear the build cache manually if required,docker buildx prunehttps://docs.docker.com/reference/cli/docker/buildx/prune/

In the sense of having a UI for deployment the advice is to go back to the CLI. That just doesn't make sense to me.

dokploy ui has a builder cleanup, which does the above, but if for some reason its not working, then you can run manually instead of having to remake your entire project

Ok, another question than. Dokploy introduced project environments (named the default env "production"), which suggests that someone would create another for staging and well maybe even another one closer to dev? But why not create a simple way to disable caching (like I said, with the flip of a switch) in those environments? Or like I said before, within every service. It's not that hard to understand why this would be a great feature in my eyes, but maybe I'm missing something. Please enlighten me if so.