It may also be a duplicate report.
This article has been translated to DeepL. There may be some awkwardness in the wording.(Translated from Korean → English)

It's hard to explain in text, so I'll use pictures to explain this issue.

We'll refer to the leftmost state as state 1 and the rightmost state as state 5.

State 1 is fine.

In state 1, if you install a block on one of the left side, right side, top, bottom, or back of the Piston, the Piston will work. Let's call this state 2.

If you destroy the blocks you installed in state 2, nothing has changed except for the blocks you destroyed. Let's call this state 3.

In state 3, you can destroy all the blocks except the Piston, and the Piston is still there. Let's call this state 4.

In either state 3 or 4, if you install a block in the place of the block you destroyed to create state 2 → 3, the Piston is restored to its original state (non-functional). Let's call this state 5.

States 2, 3, and 4 are considered bugs.

If you reshape state 4 to state 2, the Piston will not work.
In this state, destroying the block closest to the Piston, as in state 3, will cause the Piston to work.

If you destroy the Redstone Torch and the Piston in state 3, install the blocks as in state 2, and then reinstall the Piston, the Piston will not work.
If you install the Redstone Torch in this state, the Piston will not work.
In this state, if you destroy the block closest to the Piston, the Piston will work.

In state 4, installing a block on one of the left, right, top, bottom, or back of the Piston will return the Piston to a non-working state.

For sticky Pistons, the system for pulling blocks works fine.

I think this is a bug, and I'm reporting it.

//Translated with DeepL.com (free version)