How should an almost empty body in the callback handler be handled ?

[Willena]

Sometimes the "document storage service" I implemented is receiving calls to the callback endpoint with the following callback body (I replaced some values with 'xxx', others are as received):

CallbackHandlerBody{
  filetype=null, 
  url=null, 
  key='xxx',
  changesurl=null,
  history=null,
  token='xxx',
  forcesavetype=COMMAND_SERVICE, 
  status=CORRUPTED_FORCE_SAVE,
  users=["xxx"],
  actions=null,
  userdata=null, 
  lastsave='2024-12-11T15:37:04.000Z',
  notmodified=null
}

Of course when received, the webservice is not happy with this kind of body. It looks like it is missing some critical parts:

• no url
• no file type
• no change url
• no history

The question is the following: How this kind of callback body should be handled ? error ? success ? any special action to do ?

Environment: Docker, DocumentServer 8.1.1

[Willena]

After much more digging, it turn out the "converter" process was being killed in the background (due to memory usage exceeding a limit I gave at system level) .
It caused the save operation to fail in the document server.
I pretty sure this callback call should not have been made.