We have seen issues in API such /search in registration status module and same logic being called in packet receiver stage to check external status is resend.
Packet is failed with server side issues and status code will update as failed and internal work flow action will update latest transaction type code also as we have routed to workflow through came route.
When we are checking packet status ,we are checking against the latest transaction type code of other values example UPLOAD_PACKET and PACKET_RECEIVER ,but it has already overidden by workflow action transaction type code.
We will not get proper status of packet so,it will show wrong status to reg client ,even if they reupload it will fail in packet receiver stage
Sample code as follows
Refer the class /registration-processor-registration-status-service-impl/src/main/java/io/mosip/registration/processor/status/utilities/RegistrationExternalStatusUtility.java and method name getExternalStatus.
Same issue observed in
/registration-processor-registration-status-service-impl/src/main/java/io/mosip/registration/processor/status/service/impl/PacketExternalStatusServiceImpl.java also method name getExternalStatusForPacket