Pistons I was using that were stacked on top of each other didn't retract properly.

What I expected to happen was...:
I had multiple pistons stacked on top of each other with separate trails of redstone leading to each of them, not connected to each other. I expected each piston to retract when no longer connected to power.

What actually happened was...:
When deactivated in ascending order (bottom to top), each piston below one that extended stayed active, which is to say all but the top one. I tested this with pistons stacked 2 and 3 high, which had identical results. The pistons each retracted once I placed something within one block of them.

Steps to Reproduce:

The way I made this happen was with a stack of calibrated sculk sensors, each with an input of 12 redstone signal, so they only activated when a block was broken. I stacked multiple of these on top of each other, with a layer of wool between them. I then strung redstone dust from them to pistons. I have a video that you can refer to.

1. Place any block that can activate a sculk sensor when broken on the front of each piston.
2. Break each block from bottom to top.
3. The redstone will deactivate, and only the top piston will retract.

This also happens somewhat in 1.19.4, but I haven't found as easy a way to replicate it.