This relates to MC-250218, MC-250216, MC-250183, and MC-250198.

The bug:
In a multiplayer server or LAN, if a warden's target disconnects from the server it will continue to roar until that target's anger value goes below 80.

Steps to reproduce: (You don't need to create a scoreboard to see the anger value, but it can be useful visually seeing it)

• Join a multiplayer server or host one. I used Open to LAN for my testing.
• Create a scoreboard with the commands below
  /scoreboard objectives add WardenAnger dummy
  /scoreboard objectives setdisplay sidebar WardenAnger
• Inside of a repeating command block that is always active, enter this command.
  execute as @e[type=minecraft:warden,limit=1] at @s store result score AngerLevel WardenAnger run data get entity @s anger.suspects[0].anger
• Have one person observe and another person anger the warden.
• Once the warden's anger value towards a player goes above 80, (this is when the warden roars), have that player disconnect

Observed results:

• The warden will roar until the anger value of the player goes below 80.

Expected results:

• The Warden will retain it's anger value towards the disconnected player and proceed to search for more suspects.
• If a player that angered the warden disconnects and rejoins later, the warden will proceed to chase and try to kill that player.