I identified this issue after upgrading to 0.44.4.
I'm on Ubuntu 20.04 linux and using the deb package.
My day note template (and my other templates!) have iconClass specified as an attribute:

Indeed, my various templates show up in the tree with their selected icons:

However, after the upgrade, my various template instances are only displaying their default note/folder icons, but manually adding iconClass to any of them (observe the "Journal" root node) does still work.

If you're a little underwater, I'm happy to take a look at putting together a PR on this one. Trilium has been super helpful to me in just the short month I've been using it and I'm excited to be able to give back.
Hi, unfortunately I'm not able to reproduce this issue - inherited iconClass seems to work correctly for me.
Does the iconClass show up among inherited attributes in the "templated" notes, like this?

Indeed it is! Here's a screenshot from the web UI, synced with the same client.

Any particular logs that would be helpful for me to share?
That is pretty weird since Trilium seems to be aware of that inherited attribute...
Just to be sure - reload of the page in the browser does not help, right?
Refreshing did not help, no.
I changed the iconClass on the template and it did propagate out, however. Is there perhaps a cache that I invalidated in that change?
Yes, there is a cache and the code to choose icon uses it. However this cache is in frontend memory and is reloaded together with the page so reload should fix it as well.
There is also a backend cache which has longer lifetime (until restart/stop of backend) but then this cache is not used for choosing icons ...
So the mystery remains ...
Let me see if I can use anonymize-database against a backup to get you a useful repro :)
Zipped video of repro steps:
And here's a copy of the anonymized DB:
anonymized-document.zip
Just confirming that I'm currently having the same problem with 0.44.4.

Nothing strange to be seen in frontend or backend logs.
Just noticing this:
08:09:39.190 Slow POST /api/tree/load took 10ms
in the backend log, but that's probably not related?
@elementc , thanks a lot for the anonymized database, this allowed me to reproduce and fix the issue!