Skip to main content
Version: v2.6

Release 2.6.10

Issues fixed

Disposition and Impact statistics no longer crash for tracks with same-named business objects
On some tracks, opening the Disposition or Impact statistics failed to display the chart and showed an error instead of the widget. This happened when a track contained two business objects that share the same name and neither has a calling name set (for example, two Person objects).

The statistics widgets now handle same-named business objects correctly. Each one appears as its own entry in the chart and in its Business Object filter, and the widget displays as expected.

Export errors are no longer hidden by a failed key insert
During export, the Director stores the key of each dependency between items. When this key insert failed in certain ways inside the item transaction, the database procedure hid the original error. The export then stopped with the unrelated SQL error 3930, "The current transaction cannot be committed", and the real cause was lost.

The procedure now reports the original error with its true source. Recoverable situations are still handled as before: a key inserted by another process at the same moment is re-read, and deadlocks are retried when the transaction is healthy.

Note that this fix makes the real error visible so it can be addressed. If the underlying error was caused by server resources, such as a full transaction log, that condition still needs to be resolved on the server.

Cancelling a queued job now always prevents it from starting
When more jobs were submitted than the maximum number of concurrent jobs, the job next in line for a free slot could ignore a cancellation request. The job was shown as Cancelled but still started, synchronized and processed items.

The job scheduler now tracks every job through the whole hand-over from the pending queue to execution. A cancelled job can no longer start, regardless of when the cancellation arrives.

Note that cancelling a job during its synchronize step takes effect when synchronization completes. The job then stops as Cancelled and no items are processed.

Item list download no longer fails on outdated tags
When downloading the list of items, the download could fail with an error if one or more items referenced a tag that had since been removed.

The download now skips these outdated tag references and completes successfully. The affected items are still included in the file, without the missing tag.