Handle timestamp mismatch error

Content Registration XML Deposit
, , , ,
28

This one has been successfully rerun as well @mklem

https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1690776890

-Isaac

29

This looks like an error on our end. Do you have the submission ID associated with that error?

31

Hi Isaac

I still see this timestamp error almost daily and looking at our logs it seems this error happens when we send multiple requests close to each other. I am providing you with recent log info from our end in case this helps your team resolve the issue. If there is anything you need from me let me know.

Thanks for being responsive.

10.1103/m6rx-vy32
batch id: apsxref:df4bc2a2-4a01-4f54-babf-9ef0012ba8dd
date submitted: 2025-06-09
message: Successfully updated
submission id: 1700155082
submitted at: 1749478418

batch id: apsxref:9edce3d3-7df0-4700-a849-e8572191a3e2
date submitted: 2025-06-09
message: Handle timestamp mismatch, deposit: 20250609141337 handle:  index=700050 type=700050 rwr- "20250609141338" 
submission id: 1700155083
submitted at: 1749478417


===


10.1103/yf63-knqx
batch id: apsxref:925a1b4b-a90d-49d0-a6c4-aca849d8a8fa
date submitted: 2025-06-09
message: Handle timestamp mismatch, deposit: 20250609141422 handle:  index=700050 type=700050 rwr- "20250609141423" 
submission id: 1700155151
submitted at: 1749478462

batch id: apsxref:1472c4a4-6519-4378-859c-1dd047ebdd98
date submitted: 2025-06-09
message: Successfully updated" 
submission id: 1700155149
submitted at: 1749478463


===


10.1103/2jfz-wkw4
batch id: apsxref:92c26d61-caf1-42c1-a050-77636a31eac1
date submitted: 2025-06-06
message:  
submission id: 
submitted at: 1749218527

batch id: apsxref:0b12670f-b677-4b9b-ac01-313553090fc0
date submitted: 2025-06-06
message:  Record not processed because submitted version: 20250606140207 is less or equal to previously submitted version 20250606140208
submission id: 1699730157
submitted at: 1749218527

batch id: apsxref:a553e7a0-27be-4c0b-80cf-0e6b21ec8314
date submitted: 2025-06-06
message:  Handle timestamp mismatch, deposit: 20250606140207 handle:  index=700050 type=700050 rwr- "20250606140208"
submission id: 1699730152
submitted at: 1749218527

batch id: apsxref:64a78829-f55e-4824-980a-dff7225dab9b
date submitted: 2025-06-06
message:  
submission id: 
submitted at: 1749218528


===


10.1103/pqdp-x2vr
batch id: apsxref:97df22b4-df5e-4bb0-a5a8-273aaf731994
date submitted: 2025-06-05
message: Handle timestamp mismatch, deposit: 20250605172113 handle:  index=700050 type=700050 rwr- "20250605172114" 
submission id: 1699581058
submitted at: 1749144073

batch id: apsapsxref:0c3f7024-f66f-46ce-a5bc-16959461ccf83553090fc0
date submitted: 2025-06-05
message:  Successfully updated
submission id: 1699581027
submitted at: 1749144010

batch id: apsxref:ac1f95c2-0056-43ce-83c7-2d6bff81d6ca
date submitted: 2025-06-05
message:  Successfully updated
submission id: 1699580964
submitted at: 1749144008

batch id: apsxref:00a9d302-4246-408b-8f07-575b0cdaa821
date submitted: 2025-06-05
message:  Successfully updated
submission id: 1699581057
submitted at: 1749144074

===


10.1103/PhysRevLett.134.221601
batch id: apsxref:4dccd235-11b4-40e0-9981-66fd3b599af0
date submitted: 2025-06-05
message: Handle timestamp mismatch, deposit: 20250605140117 handle:  index=700050 type=700050 rwr- "20250605140120" 
submission id: 1699559929
submitted at: 1749132077

batch id: apsxref:63ce0c79-befd-492f-9ec8-0af722cfdd15
date submitted: 2025-06-05
message:  
submission id: 
submitted at: 1749132076

batch id: apsxref:02541717-b5c3-42b2-a430-ea08bf880d3d
date submitted: 2025-06-05
message: Successfully updated 
submission id: 1699559926
submitted at: 1749132080

batch id: apsxref:0664167c-0e94-4966-a380-00864ffb43a6
date submitted: 2025-06-05
message: Successfully updated 
submission id: 1699559797
submitted at: 1749132074

batch id: apsxref:dbdccb6e-d520-47de-a7b5-5c28368e2592
date submitted: 2025-06-05
message: Successfully updated 
submission id: 1699559803
submitted at: 1749132075

batch id: apsxref:apsxref:dbdccb6e-d520-47de-a7b5-5c28368e2592
date submitted: 2025-06-05
message: org.springframework.dao.DeadlockLoserDataAccessException: PreparedStatementCallback; SQL [UPDATE atypon.citation_info SET JOURNALCITEID = ?, BOOKCITEID = ?, SERIESTITLEID = ?, MISSPELLINGID = ?, SUBMISSIONID = ?, VERSION = ?, YEAR = ?, VOLUME = ?, ISSUE = ?, SUPPLEMENT = ?, PAGE = ?, AUTHOR = ?, COMPONENTNUMBER = ?, EDITIONNUMBER = ?, OWNERPREFIX = ?, ARTICLETITLE = ?, SEQUENCENUMBER = ?, TYPE = ?, DOI = ?, MDCONFLICTID = ?, PAGEMOD = ?, SRCTYPE = ?, ORIGPAGE = ?, LASTPAGE = ?, PUBMONTH = ?, PUBDAY = ?, CONFNAMEID = ?, INSTCITEID = ?, FORCEDALIASID = ?, SRCSUBTYPE = ?, LASTUPDATE = ?, UNIXMLSTATUS = ?, UNICLOBID = ?, MASK = ?, ALIASID = ? WHERE CITATIONID = ?]; ERROR: deadlock detected
  Detail: Process 1957995 waits for ShareLock on transaction 432234721; blocked by process 1958559.
Process 1958559 waits for ShareLock on transaction 432234723; blocked by process 1957995.
  Hint: See server log for query details.
  Where: while updating tuple (6491268,22) in relation "citation_info"; nested exception is org.postgresql.util.PSQLException: ERROR: deadlock detected
  Detail: Process 1957995 waits for ShareLock on transaction 432234721; blocked by process 1958559.
Process 1958559 waits for ShareLock on transaction 432234723; blocked by process 1957995.
  Hint: See server log for query details.
  Where: while updating tuple (6491268,22) in relation "citation_info" 
submission id: 1699559804
submitted at: 1749132078
33

Hi @mklem ,

Thanks for these examples.

Yes, the submission of the same DOI very close together can cause these handle timestamp errors.

Starting with that first DOI example 10.1103/m6rx-vy32, how is the XML different between submissions 1700155082 and 1700155083? What is being added or modified to the metadata record in submission 1700155083 that was absent or less rich in 1700155082?

Thanks for those additional details,
Isaac