Do quarto preview use jupyter caches even if disabled in frontmatter?

[kompre]

Description

I'm having a maddening time with a document that is not rendering correctly when using quarto preview (via vscode ctrl+shift+K).

The document is a book type and I have specified for each chapter (qmd) the executing option:

execute:
 cache: true

The documents consist also of many ipynb heavy with computations, and in some there are inline python expression. Then I convert the ipynb in proper qmd files[^1] and run the preview.

I can see in the terminal that document that should be executed both because the source file is changed and because the it is specified in execution setting, do not run and the pdf output is in fact incorrect, with the still the outdated content, therefore must have used

When I run quarto render instead the documents are properly executed, and pdf output is correct.

Why the preview act like that? How it differs from the rendering process? Can someone please explain how does it work? Does make any difference setting the execution per each file?

[^1] : the ipynb source file where I actually write are converted to qmd with the quarto utility and also the name is changed, to avoid conflict when running the preview/render