Bug Instancing particle strip broken

I did some tests for both particles and trails with instancing enabled and there was no problem so far, but today I decided to create bullet trail and for some reason it does not work. I thought this is related to my pooling system, but when I unticked "allow instancing", then all trails started to work as expected.

Spoiler: Graph

When instancing is enabled then only one trail is rendered, sometimes:


Also, additional question - is there really no way to enforce all trails/particles to be rendered at once?
I mean, if I know there is no problem with sorting, particles are additive or specific order is introduced, then rendering with depth sorting could be skipped. Well, actually I had no chance to profile GPU side, so that might be not a problem, but it in any case it would be great to somehow reduce CPU cost, because currently it seems to run super slow.
Example based on my projectiles: there are around 200 bullets and each of them has vfx instance to generate trail. Currently to update VFX of those trails (only) it requires more than 5ms.

Obviously I could create some global manager and render all trails with single system, but it is way easier to just drop vfx into some prefab, than create complex system for various types of trails of whatever else.

 

Aww, sorry for confusion, I guess the profiler screenshot was made with instancing disabled as I tried again and this is how it looks like:

However, even if those numbers represent actual performence, currently it renders only 1 trail, so it simply does not work.

The good thing is I found what caused the bug, it is caused by Spawn Over Distance block, as I tried potato workaround like this and it renders more than 1 trail:



I assume spawn over distance breaks batching as it runs on CPU or something related that.