There should be a way to identify which container/host instance of the federation service is sending messages that fail to be processed by the API consumer so that if one specific instance seems to be having issues it can be restarted/killed/whatever to try to resolve problems (or pulled out of rotation and investigated)
There should be a way to identify which container/host instance of the federation service is sending messages that fail to be processed by the API consumer so that if one specific instance seems to be having issues it can be restarted/killed/whatever to try to resolve problems (or pulled out of rotation and investigated)