# Received SQL error

**URL:** <https://community.crossref.org/t/received-sql-error/13869>\
**Category:** Technical Support\
**Tags:** content-registration, deposit\_support\
**Created:** [29 May 2025 15:43 UTC](https://community.crossref.org/t/received-sql-error/13869 "2025-05-29T15:43:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mklem](https://avatars.discourse-cdn.com/v4/letter/m/65b543/32.png) [@mklem](https://community.crossref.org/u/mklem)\
**Post date:** [29 May 2025 15:43 UTC](https://community.crossref.org/t/received-sql-error/13869/1 "2025-05-29T15:43:31Z")

</div>

I received an error from Crossref:

| **batch\_id:** | apsxref:82eb80a2-48e9-4abc-83f6-0c14379496cb |
| --- | --- |
| **doi:** | 10.1103/PhysRevD.111.094041 |
| **msg:** | PreparedStatementCallback; uncategorized SQLException for SQL [insert into xref.general\_rels (CLAIMANT\_ID,CLAIMANT\_CITEID,CLAIMANT\_TYPE,DESCRIPTION,DELETED,RECORD\_UPDATED,TARGET\_CITEID,TARGET\_ID,TYPE) values (?, ?, ?, ?, ‘N’, ?, ?, ?, ?) on conflict do nothing]; SQL state [25P02]; error code [0]; ERROR: current transaction is aborted, commands ignored until end of transaction block; nested exception is org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block |
| **submission\_id:** | 1698678185 |

I assume this is an error we should not receive.

Should I try resending this DOI?

---

<div class="post-metadata">

**Author:** ![Shayn](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/shayn/32/57_2.png) [@Shayn](https://community.crossref.org/u/Shayn)\
**Post date:** [29 May 2025 16:52 UTC](https://community.crossref.org/t/received-sql-error/13869/2 "2025-05-29T16:52:01Z")

</div>

Hello, and thanks for your message.

Yes, that was definitely an error on our end. I re-ran submission 1698678185 now, to save you the trouble of having to resend it. It’s been reprocessed successfully now.

If you see any other submissions with a SQLException type error, resubmitting them does typically solve the problem. But, if it ever doesn’t, let us know, and we’ll ask our technical team to investigate further.

Best,  
Shayn