workflowEventID violated | Community
Skip to main content
Level 6
January 17, 2024
Solved

workflowEventID violated

  • January 17, 2024
  • 2 replies
  • 668 views

How to address the above issue? Whenever I try to run the workflow, I'm getting this error.I don't see any duplicate entries in the table either

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Parvesh_Parmar

Hello @sanjana12 ,

 

WorkflowEventID serves as the primary key for the out-of-the-box xtk:workflowEvent table, utilizing the XtkWorkflowEventId pksequence to manage its primary key generation.

 

 

 

 

Upon running a workflow, an entry is created in this table. The issue you're encountering may arise when the newly generated ID already exists.

To address this, consider adjusting the pksequence value to the maximum existing PK value in your table. By doing so, the subsequent ID generated will start from a value beyond the existing maximum.

 

For instance, if the maximum PK value in the workflow event table is 210234, you can set the pksequence value to 210240. This adjustment ensures that the next ID generated will begin from 210240, potentially resolving the workflowEventID violation.

 

 

 

Kr,

Parvesh

2 replies

Parvesh_Parmar
Community Advisor
Parvesh_ParmarCommunity AdvisorAccepted solution
Community Advisor
January 19, 2024

Hello @sanjana12 ,

 

WorkflowEventID serves as the primary key for the out-of-the-box xtk:workflowEvent table, utilizing the XtkWorkflowEventId pksequence to manage its primary key generation.

 

 

 

 

Upon running a workflow, an entry is created in this table. The issue you're encountering may arise when the newly generated ID already exists.

To address this, consider adjusting the pksequence value to the maximum existing PK value in your table. By doing so, the subsequent ID generated will start from a value beyond the existing maximum.

 

For instance, if the maximum PK value in the workflow event table is 210234, you can set the pksequence value to 210240. This adjustment ensures that the next ID generated will begin from 210240, potentially resolving the workflowEventID violation.

 

 

 

Kr,

Parvesh

Parvesh Parmar – Adobe Community Advisor https://www.linkedin.com/in/parvesh-parmar/
Adobe Employee
January 20, 2024

Hi @sanjana12 ,

 

Refer to this post for making the data type of id from 32-bit to 64-bit integer. This will increase the value.


Raise a support ticket with Adobe as changing the ootb schemas sequence needs to be done with care.