repmgr cluster config showing incorrect status

[vhpriya16]

Hi,

We are seeing incorrect 'status' in the repmgr cluster config on one of our standby nodes.

ID | Name | Role | Status | Upstream | Location | Connection string
----+----------------+---------+----------------------+-------------+----------+-----------------------------------------------------------------------------------------------------------------------------------------
1 | wic_1 | standby | running | wic_3 | default | host=host1.com port=8000 passfile=/opt/app/postgres/.pgpass user=repmgr dbname=repmgr connect_timeout=2
2 | wic_2 | standby | ! running as primary | wic_3 | default | host=host2.com port=8000 passfile=/opt/app/postgres/.pgpass user=repmgr dbname=repmgr connect_timeout=2
3 | wic_3 | primary | ? unreachable | | default | host=host3.com port=8000 passfile=/opt/app/postgres/.pgpass user=repmgr dbname=repmgr connect_timeout=2
4 | wic_4 | standby | running | wic_3 | default | host=host4.com port=8000 passfile=/opt/app/postgres/.pgpass user=repmgr dbname=repmgr connect_timeout=2
5 | wic_wit | witness | * running | wic_3 | default | host=host5.com port=8000 passfile=/opt/app/postgres/.pgpass user=repmgr dbname=repmgr connect_timeout=2

what causes such discrepancy in the node status ?
how can we fix this ?

repmgr version being used is repmgr 4.0.6
shows currently on primary and other standby nodes