E-Mail Message:

Text	Picture

Text	Picture
name: OTCS_wlock expr: oracledb_otcs_wlock_count for: 4h labels: HID: OTCS3001 Help: OTCS3001 Workflow Wlock Table severity: P2 severity_desc: High team: hit-opsgenie annotations: description: They dont change the State since 4h summary: Content Server has Workflows in Wlock Table(instance {{ $labels.instance }})

Applies to

System	Version	Approved

System	Version	Approved
opentext Content Server	16.x	Yes
opentext Content Server	20.x	Yes
opentext Content Server	21.x	Yes
opentext Content Server	22.x	Yes
opentext Content Server	23.x	open
opentext Content Server	24.x	open

Summary

.There are various situations in which Content Server may lock a workflow instance, such as when a user suspends the workflow or when Content Server experiences a crash. In these cases, it becomes impossible for other users, including the Admin user, to modify the status of the locked workflow. Specifically, the user will be unable to proceed with a workflow step by selecting "Send On", or they will not be able to halt or remove a workflow from the Workflow Status section found in the Personal menu > Workflows.

Solution

Delete the Workflow ID from the Wlock Table

delete from wlock where wlock_workid in ('workid','workid')

Sources of Errors

In Content Server, error messages may be encountered when attempting to perform actions such as "Send On", "Stop", or "Delete" on a locked workflow instance

KB Referenz

Support articles, alerts & useful tools - Content Server - Extractor not processing items (regardless whether incremental indexing or full reindexing) (opentext.com)