NodeNetworkConfigurationPolicy created successfully but after 2 days the status change from available to degraded

$ oc get nncp  egress-policy3 
NAME             STATUS     REASON
egress-policy3   Degraded   FailedToConfigure 

the NNCP add a simple route-rule below

spec:
  desiredState:
    route-rules:
      config:
      - ip-to: 100.79.228.64/27
        priority: 5550
        route-table: 254
  nodeSelector:
    node-role.kubernetes.io/gateway: ""    

NNCP message status : 1/2 nodes failed to configure 

status:
  conditions:
  - lastHeartbeatTime: "2024-08-14T11:36:57Z"
    lastTransitionTime: "2024-08-14T11:36:57Z"
    reason: FailedToConfigure
    status: "False"
    type: Available
  - lastHeartbeatTime: "2024-08-14T11:36:57Z"
    lastTransitionTime: "2024-08-14T11:36:57Z"
    message: 1/2 nodes failed to configure
    reason: FailedToConfigure
    status: "True"
    type: Degraded  

kubernetes-nmstate-operator.4.14.0-202406180839 4.14.0-202406180839    
ocp: 4.14.29

    Not always

    1. Deploy NNCP to add route-rules for egress IP
    2. Check NNCP status is available 
    3. Wait sometime 1 or 2 days and check NNCP status
    

    NodeNetworkConfigurationPolicy status change from available (reason:SuccessfullyConfigured) to degrade as 1 of the node config

    NodeNetworkConfigurationPolicy status is available and reason SuccessfullyConfigured

    1 restart of the nmstate-handler pod fixed the issue for one of their ocp cluster, but for the second cluster multiple restart of the pod were done to get the nncp status to available.