The /setblock command does not create blocks using the blockstates defined by the user in their command, instead the placed block will change some of its blockstates to be the same as if the block had been placed by a hand.

Below I have a few examples comparing 1.15 to 1.16 this most likely is not a list that contains all of the blockstates which are ignored upon creating a block with /setblock but it should hopefully give you a good idea of what the issue is so that it can be fixed.

Stairs:

Ignored blockstates - "shape"

Command used in example - "/setblock ~-3 ~ ~ minecraft:oak_stairs[facing=west, half=bottom, shape=inner_left, waterlogged=false]"

Fence / Iron bars / Glass Pane:

Ignored blockstates - "north", "east", "south", "west"

Command used in example - "/setblock ~-3 ~ ~ minecraft:{oak_fence/iron_bars/glass_pane}[north=true, south=true, east=false, west=false, waterlogged=false]"

Wall:

Ignored blockstates - "up", "north", "east", "south", "west"

Command used in 1.15 example - "/setblock ~-3 ~ ~ minecraft:cobblestone_wall[north=true, south=true, east=false, west=false, waterlogged=false]"

Command used in 1.16 example - "/setblock ~-3 ~ ~ minecraft:cobblestone_wall[up=false, north=tall, south=low, east=none, west=none, waterlogged=false]"

Fence gate:

Ignored blockstates - "in_wall"

Command used in example - "/setblock ~-3 ~ ~ minecraft:oak_fence_gate[facing=east, open=false, in_wall=false, powered=false]"