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.
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.
aWarm regards,
Isaac
Thanks Isaac.
How does the timestamp get out of sync? How often does this happen?
Thank you
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
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.
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://0-doi-crossref-org.library.alliant.edu/servlet/submissionAdmin?sf=detail&submissionID=1661918171
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
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
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
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 |
Hello @mklem ,
I have manually reset that DOI’s timestamp and have successfully reprocessed submission https://0-doi-crossref-org.library.alliant.edu/servlet/submissionAdmin?sf=detail&submissionID=1668582338.
-Isaac
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 |
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://0-doi-crossref-org.library.alliant.edu/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
Thanks for clarifying,
Isaac
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.
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://0-doi-crossref-org.library.alliant.edu/servlet/submissionAdmin?sf=detail&submissionID=1675695711.
-Isaac
Thanks Isaac.
Do other folks experience this issue? I feel because of our process, it is more common.
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
