A template now uses an instance rather than it's definition for creating new instance

[fragefrank]

I have a template that behaves oddly. It is defined attributed with empty fields. After creating multiple instances and filling their fields, for some reason, new instances now use one of the old instances as basis, with their filled in values, rather than the template definition with empty fields. How could I fix this ?

[Davide_Di_Ruscio]

I have the same problem. In the past it was properly working.

[fragefrank]

I’ll file a bug report then, linking to this thread: new instances of template created from a former instance instead of the template definition · Issue #9250 · logseq/logseq (github.com)

[Junyi_Du]

Does clear cache help?

How to Clear Cache in Logseq?

Step 1: Confirm where your data located: Logseq would ask you to pick a folder on startup: [image] Finds out the folder (for example, the folder docs here), it typically CONTAINS folders like journals logseq pages INSIDE: [image] (Using the Logseq document graph as example) REMEMBER the location of the folder ITSELF (e.g. the folder docs in this example, but not the folders inside!). May do some backup if you like [image] If you forget where the folder is, here’s an easy way to…

[fragefrank]

Tried - no, it doesn’t solve it. Still get new templates instantiated with an old one.

[fragefrank]

Now I’m getting this error - does this make sense to anyone ?

Template insert error: Conflicting upserts: [:block/uuid #uuid “65292499-195b-41a0-879e-231724257a49”] resolves to 79441, but [:block/original-name “Is Our Definition Of Burnout All Wrong?”] resolves to 33671