Sdoc can not save back to seafile

Seafile Comm 11.0.3 + SeaDoc 0.4:
1、ceate a new empty sdoc file in seafile web
2、click and open this sdoc file in seafile web
3、input something,get saved success tip in top area
4、back seafile, no updated, still a empty sdoc file

seahub.log
2024-01-18 15:43:00,877 [ERROR] seahub.seadoc.apis:169 post save sdoc failed 2cef5ddf-cc73-4397-a95d-77debf977166, {“error”: “No target_file given.”}
2024-01-18 15:43:00,879 [WARNING] django.request:241 log_response Bad Request: /api/v2.1/seadoc/upload-file/2cef5ddf-cc73-4397-a95d-77debf977166/

We cannot reproduce the issue with a newly installed Seafile Comm 11.0.3 + SeaDoc 0.4.

catch the request from sdoc-server to seafile, and to fileserver(upstream by nginx)

modify /opt/seafile/seafile-server-latest/seahub/seahub/seadoc/apis.py, get request info:
post: https://xxx:34443/seafhttp/update-api/2a2e067a-a0f7-4605-b143-89008533d109
body: {‘file’: <InMemoryUploadedFile: 0676d5b3-a51b-436b-9209-bdb32f4df148 (application/octet-stream)>, ‘file_name’: ‘q.sdoc’, ‘target_file’: ‘/q.sdoc’}

log by nginx(upstream to fileserver https://xxx:34443/seafhttp/xxx), it seemed ok:
–92679c92049d84f7ffd452b7b3195148
Content-Disposition: form-data; name=“file”; filename=“9b4e773d-1c47-4bc2-9af0-730d477e371b”

{“version”:104,“format_version”:3,“children”:[{“id”:“K_eIFWIuScmeDO02ZfOUIA”,“type”:“paragraph”,“children”:[{“id”:“QaZbBeg6TmS721cyYhejGw”,“text”:“123123123”}]}],“last_modify_user":"cloud@wangjia.net”}
–92679c92049d84f7ffd452b7b3195148
Content-Disposition: form-data; name=“file_name”; filename=“file_name

q.sdoc
–92679c92049d84f7ffd452b7b3195148
Content-Disposition: form-data; name=“target_file”; filename=“target_file

/q.sdoc
–92679c92049d84f7ffd452b7b3195148–

why fileserver report “No target_file given.”
I have delete seafile and sdoc server docker images, and re-pull from docker hub, it still not work.