# Handle timestamp mismatch error **URL:** \ **Category:** XML Deposit\ **Tags:** timestamp, content-registration, xml\_support, deposit\_support, cnri\ **Created:** [16 December 2024 18:11 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815 "2024-12-16T18:11:18Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![mklem](https://avatars.discourse-cdn.com/v4/letter/m/65b543/32.png) [@mklem](https://community.crossref.org/u/mklem)\ **Post date:** [16 December 2024 18:11 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/1 "2024-12-16T18:11:18Z")
Received this Crossref error message: batch\_id apsxref:0db3c004-fda3-46cd-80ce-91302738396c doi 10.1103/PhysRevD.110.103017 msg Handle timestamp mismatch, deposit: 20241213162421 handle: index=700050 type=700050 rwr- “20241213162424” submission\_id 1660807780 What does this error indicate? Hiow does it differ from other timestampt errors? Trying to understand if I can ignore this error. ---
**Author:** ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)\ **Post date:** [16 December 2024 22:44 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/2 "2024-12-16T22:44:58Z")
Hi @mklem , This one is also a rare error. It happens when the timestamps in our system get out of sync with the timestamp stored in the handle system. I have reset the timestamp in our system, which normally does the trick, and have re-pushed the submission - 1660807780. The DOI has now been successfully updated. ![Screenshot 2024-12-16 at 4.43.47 PM](https://us1.discourse-cdn.com/flex020/uploads/crossref/original/2X/1/1b7159e120cc5cc9715ed9707cb08190f7b3d580.png)a Warm regards, Isaac ---
**Author:** ![mklem](https://avatars.discourse-cdn.com/v4/letter/m/65b543/32.png) [@mklem](https://community.crossref.org/u/mklem)\ **Post date:** [17 December 2024 01:24 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/3 "2024-12-17T01:24:12Z")
Thanks Isaac. How does the timestamp get out of sync? How often does this happen? Thank you ---
**Author:** ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)\ **Post date:** [17 December 2024 20:19 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/5 "2024-12-17T20:19:30Z")
Hi @mklem , While very rare, the timestamps can get out of sync because these are two systems and sometimes they have communication errors (e.g., a temporary connection issue). Like I said, they’re very rare. We typically get a couple of tickets about this every year. Warm regards, Isaac ---
**Author:** ![mklem](https://avatars.discourse-cdn.com/v4/letter/m/65b543/32.png) [@mklem](https://community.crossref.org/u/mklem)\ **Post date:** [20 December 2024 17:00 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/7 "2024-12-20T17:00:51Z")
Hi Isaac, Got another timestampt mismatch error this morning: {“batch\_id”:“apsxref:51bf989d-47f5-498b-8c35-c000bc9a934b”,“doi”:“10.1103/PhysRevFluids.9.123801”,“msg”:“Handle timestamp mismatch, deposit: 20241220154133 handle: index=700050 type=700050 rwr- "20241220154134"”,“submission\_id”:“1661918171”} Can I just ignore these or resubmit the XML data when I get these errors? Wondering if there is something I can do on my end to retry in this case. ---
**Author:** ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)\ **Post date:** [20 December 2024 19:10 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/8 "2024-12-20T19:10:01Z")
Thanks for flagging this to us @mklem. Well, this is concerning to have a couple of these errors in such close proximity. I am going to ask our technical team to take a look to see if we might have a bug or larger problem. As I said, there are typically quite rare. I have reset your timestamp and successfully reprocessed submission [https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1661918171](https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1661918171) ![Screenshot 2024-12-20 at 1.08.45 PM](https://us1.discourse-cdn.com/flex020/uploads/crossref/original/2X/1/1c4fbcae938ef861d522df40dc7c04cabd452f93.png) Unfortunately, you can’t simply resubmit these to avoid the timestamp error. We first need to intervene to reset the timestamp in our system (in order to resync the two systems). That said, there may be a larger systems issue here that I have asked our technical team to investigate. -Isaac ---
**Author:** ![mklem](https://avatars.discourse-cdn.com/v4/letter/m/65b543/32.png) [@mklem](https://community.crossref.org/u/mklem)\ **Post date:** [2 January 2025 20:11 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/11 "2025-01-02T20:11:02Z")
> [@mklem](#): > > Handle timestamp mismatch Hi Isaac, I received this timestamp error on Dec 30: batch\_id apsxref:558b9ba8-159e-47cc-9805-b9afaa6c5b00 doi 10.1103/PhysRevLett.133.266201 msg Handle timestamp mismatch, deposit: 20241230152734 handle: index=700050 type=700050 rwr- “20241230152737” submission\_id 1663559230 ---
**Author:** ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)\ **Post date:** [2 January 2025 21:17 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/13 "2025-01-02T21:17:20Z")
> [@mklem](#): > > 1663559230 I have reset the timestamp of DOI 10.1103/PhysRevLett.133.266201 and have successfully reprocessed submission 1663559230. I have also flagged this as another example of this problem. Our technical team has not yet had an opportunity to investigate the underlying cause. -Isaac ---
**Author:** ![mklem](https://avatars.discourse-cdn.com/v4/letter/m/65b543/32.png) [@mklem](https://community.crossref.org/u/mklem)\ **Post date:** [27 January 2025 15:16 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/15 "2025-01-27T15:16:58Z")
Hi Isaac, Here is another one: | **batch\_id:** | apsxref:b9f23f7d-c50e-4ad6-b2a1-70a82294e951 | | --- | --- | | **doi:** | 10.1103/PhysRevD.110.116017 | | **msg:** | Handle timestamp mismatch, deposit: 20250127150910 handle: index=700050 type=700050 rwr- “20250127150912” | | **submission\_id:** | 1668582338 | ---
**Author:** ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)\ **Post date:** [27 January 2025 19:07 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/16 "2025-01-27T19:07:40Z")
> [@mklem](#): > > 1668582338 Hello @mklem , I have manually reset that DOI’s timestamp and have successfully reprocessed submission [https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1668582338](https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1668582338). -Isaac ---
**Author:** ![mklem](https://avatars.discourse-cdn.com/v4/letter/m/65b543/32.png) [@mklem](https://community.crossref.org/u/mklem)\ **Post date:** [18 February 2025 17:59 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/17 "2025-02-18T17:59:56Z")
Hi Issac, This error came in this morning: | batch\_id | apsxref:fce4b510-1b25-49d8-a871-8d42cd31c328 | | --- | --- | | doi | 10.1103/PhysRevD.111.024066 | | msg | Handle timestamp mismatch, deposit: 20250218151122 handle: index=700050 type=700050 rwr- 20250218151124 | | submission\_id | 1675695711 | ---
**Author:** ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)\ **Post date:** [18 February 2025 21:22 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/18 "2025-02-18T21:22:58Z")
> [@mklem](#): > > 1675695711 I looked into this further with this example @mklem . We processed an update for DOI 10.1103/PhysRevD.111.024066 right at the same time that submission 1675695711 returned this handle timestamp mismatch error (10:11 am ET). That successful submission for this DOI is: [https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1675695709](https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1675695709) I think those simultaneous submissions are causing this error. Were you intending on sending us an update for this DOI with file name apsxref:fce4b510-1b25-49d8-a871-8d42cd31c328 AND apsxref:db8df809-98b7-46fc-ba2f-674bc36c4ae5 ![Screenshot 2025-02-18 at 3.21.13 PM](https://us1.discourse-cdn.com/flex020/uploads/crossref/original/2X/c/c1a56074c094a1b4e285baf63a5366a5f1f36df5.png) ![Screenshot 2025-02-18 at 3.21.22 PM](https://us1.discourse-cdn.com/flex020/uploads/crossref/original/2X/6/6e7562325eadbd04c5fa0b331063a5840c76777d.png) Thanks for clarifying, Isaac ---
**Author:** ![mklem](https://avatars.discourse-cdn.com/v4/letter/m/65b543/32.png) [@mklem](https://community.crossref.org/u/mklem)\ **Post date:** [18 February 2025 22:53 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/19 "2025-02-18T22:53:41Z")
Hi Isaac, Sorry, I didn’t see your email until now. It is possible that someone was trying to update this at the same time. ---
**Author:** ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)\ **Post date:** [19 February 2025 17:50 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/20 "2025-02-19T17:50:03Z")
Okay @mklem . So, the two submissions would have come from different people or departments then (and, thus, not an opportunity for process improvement)? Those other examples where this error was triggered also were due to two simultaneous submissions of the same DOI. I have reset the timestamp of DOI 10.1103/PhysRevD.111.024066 and successfully reprocessed submission [https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1675695711](https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1675695711). -Isaac ---
**Author:** ![mklem](https://avatars.discourse-cdn.com/v4/letter/m/65b543/32.png) [@mklem](https://community.crossref.org/u/mklem)\ **Post date:** [19 February 2025 19:53 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/21 "2025-02-19T19:53:15Z")
Thanks Isaac. Do other folks experience this issue? I feel because of our process, it is more common. ---
**Author:** ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)\ **Post date:** [19 February 2025 20:18 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/22 "2025-02-19T20:18:58Z")
> [@ifarley](#): > > Do other folks experience this issue? It is very rare. For this handle timestamp issue, American Physical Society (APS) is the only member I have had to reset timestamps against in 2025. > I feel because of our process, it is more common. Yes, agreed. We did make some changes to our database in late 2024 that has made submission processing in our system more efficient (faster), which we think is also related and why we’re seeing more of these for APS submissions. -Isaac ---
**Author:** ![mklem](https://avatars.discourse-cdn.com/v4/letter/m/65b543/32.png) [@mklem](https://community.crossref.org/u/mklem)\ **Post date:** [11 April 2025 20:27 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/23 "2025-04-11T20:27:02Z")
Hi Isaac, Here are two submissions that experienced this timestamp issue: | **batch\_id:** | apsxref:58701049-3762-4c25-a160-380e98088874 | | --- | --- | | **doi:** | 10.1103/PhysRevD.111.083018 | | **msg:** | Handle timestamp mismatch, deposit: 20250411140452 handle: index=700050 type=700050 rwr- “20250411140457” | | **submission\_id:** | 1689735909 | | **batch\_id:** | apsxref:c26ac88f-5465-4f8f-9456-d48496b24922 | | --- | --- | | **doi:** | 10.1103/PhysRevD.111.075010 | | **msg:** | Handle timestamp mismatch, deposit: 20250410141146 handle: index=700050 type=700050 rwr- “20250410141149” | | **submission\_id:** | 1689269649 | Thanks ---
**Author:** ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)\ **Post date:** [14 April 2025 12:46 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/25 "2025-04-14T12:46:17Z")
> [@mklem](#): > > 1689269649 and 1689735909 Hello @mklem , I have successfully rerun both of these submissions ([https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1689269649](https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1689269649) and [https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1689735909](https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1689735909)) for you. -Isaac ---
**Author:** ![mklem](https://avatars.discourse-cdn.com/v4/letter/m/65b543/32.png) [@mklem](https://community.crossref.org/u/mklem)\ **Post date:** [14 April 2025 15:47 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/26 "2025-04-14T15:47:44Z")
Hi Isaac. Thanks for helping with the previous timestamp issues. Here is one more: | **batch\_id:** | apsxref:0fa3dfe7-f518-4635-ac96-591639c4f5c8 | | --- | --- | | **doi:** | 10.1103/PhysRevD.111.074020 | | **msg:** | Handle timestamp mismatch, deposit: 20250414140341 handle: index=700050 type=700050 rwr- “20250414140343” | | **submission\_id:** | 1690776890 | Much appreciated. ---
**Author:** ![mklem](https://avatars.discourse-cdn.com/v4/letter/m/65b543/32.png) [@mklem](https://community.crossref.org/u/mklem)\ **Post date:** [14 April 2025 15:54 UTC](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815/27 "2025-04-14T15:54:09Z")
> [@mklem](#): > > apsxref:0fa3dfe7-f518-4635-ac96-591639c4f5c8 I also noticed that this was sent multiple times and will see if there is some way to prevent these errors or if we can ignore them. I also noticed this error was received from your end: 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 509671 waits for ShareLock on transaction 357769457; blocked by process 509793. Process 509793 waits for ShareLock on transaction 357769545; blocked by process 509671. Hint: See server log for query details. Where: while updating tuple (3991674,8) in relation “citation\_info”; nested exception is org.postgresql.util.PSQLException: ERROR: deadlock detected Detail: Process 509671 waits for ShareLock on transaction 357769457; blocked by process 509793. Process 509793 waits for ShareLock on transaction 357769545; blocked by process 509671. Hint: See server log for query details. Where: while updating tuple (3991674,8) in relation “citation\_info” [Next page](https://community.crossref.org/t/handle-timestamp-mismatch-error/12815.md?page=2)