Closed whippersnapper closed 7 years ago
That is a strange error since I am catching these, can you search for messages or mdns with that message ID?
@abhishek-ram it never made to the MDN sends. There is no messages generated. If the save would of gone through, then I believe that is the next step (generating the MDN).
I wanted to note that the transfer encoding is content-transfer-encoding: binary
is this supported?
I saw that in the source code, you've made a comment about composite key? I wonder if that would help?
Yeah the composite key would help, but you are saying that you are not even able to find another message with this ID so I am not sure what issue this is. Yes the binary encoding is supported.
I figured out what the problem was. The incoming message id surpassed the model max_length settings (currently set to 100). The incoming partner's message was over that. Django seems to just auto trucate by default and carry on. That caused some weird behaviors on the save()
as it tries to insert again vice upsert.
Okay should i go ahead and increase the size and release a patch?
Can anyone help to explain why the server throws exception on a particular inbound receive? Someone is sending to us a X12 formatted payload. We are getting the following exception. Seems to be duplicate key? I'm not quite sure why this is happening.