Summary

When the execution of a task through the Scheduler fails due to an overflow error, It is very likely because one of the Bizagi’s tables has reached the maximum value allowed for its IDENTITY field. Due this error, the activity is not completed. 

Applies to

Bizagi 10.x 

Symptoms

Error message found in the Event Viewer and the Scheduler log:

Cause

The error occurs when the range of the IDENTITY column in the table ASYNCHWORKITEMRUNNING has exceeded the limit value. Due to the total number of registries inserted to the table, regardless of the datatype of the IDENTITY column. 

For example, if the IDENTITY column datatype is set as tinyint, there are 255 possible values before an overflow error shows up.

Solution

Delete all the rows in the ASYNCHWORKITEMRUNNING table and then, reset the increment counter of the table by using RESEED command. It is important that the table is not truncated to avoid data inconsistencies. 

Use the command below to reset the values after rows deletion:

DBCC CHECKIDENT ('ASYNCHWORKITEMRUNNING', RESEED, 0)

Where RESEED, 0 means that the next value for the IDENTITY will be 1. It will increment on each insertion.

You can find more information about DBCC CHECKIDENT command in the following link:
https://msdn.microsoft.com/en-us/library/ms176057.aspx