podman ps takes a long time (5+ minutes) to detect a killed container & its 'conmon' OCI runtime wrapper, can it be tweaked to be more responsive?

I am running podman version 5.4.0 on Rocky Linux 9.6. I notice that when a container is killed along with its 'conmon ' OCI runtime wrapper, say by issuing a kill -9, the podman ps command does not detect the dead container for a good 5 minutes+. In the intervening time, the command lists the container as being up even as other commands like podman stats , podman exec all fail pointing correctly to the container as being dead in the error message! $ podman ps -a | grep kafka 7fd65b99d2a0 localhost/****/cp-kafka:*.*.* /etc/confluent/do... 39 hours ago Up 37 hours 9092/tcp kafka $ podman exec -it 7fd65b99d2a0 bash Error: OCI runtime error: crun: the container 7fd65b99d2a06252078fc85d3c9832d4c1410e0d185bb9cde08c6641aca31334 is not running $ podman stats 7fd65b99d2a0 Error: cannot get cgroup path unless container 7fd65b99d2a06252078fc85d3c9832d4c1410e0d185bb9cde08c6641aca31334 is running: container is stopped I understand the parent runtime monitor is also killed but i am not sure if that justifies reporting an incorrect status in the podman ps command. Is that the expected behavior? Can this be tweaked in some way to be more responsive?