This one was the Workload report (see attached screenshot). If we close out of the instances list and then reopen the "locked" instances will be back to normal (completed/in progres...) and the August instances will be gone. Sometimes we have to close/reopen a couple of times before if is corrected.

Sorry, attached screenshot here.

Thank you for the information! We will try to reproduce the issue on our side and investigate the root cause.

Hi Cassandra, a quick update: this issue has been passed to development team. For now, if you want to get rid of the lock status, you could try the following two workarounds:

• Find out the instances contain the locked tasks from instances list, open the instances details and reassign the task to another user then reassign back to the original user, the original user can submit form again to complete the task.
• Find out the instances contain the locked tasks from instances list, use the new skip action in Forms 10.4.2 to skip those locked user tasks to move to next step.

Thank you for the update! Just some additional info for the dev team:

We've found that the tasks that are locked were in instances that have already been completed (we have not continued to verify this once reporting the issue). It's why we were so confused they were showing status locked.

Please let me know if you'd like us to do further testing to assist.

Is there a SQL query we can run against the Forms database to find all Locked tasks?

Reviving Blake's question, as I ran into this recently as well.  Unfortunately, the instances were manually resolved so I can't do this anymore however I assume it's the values within [LF_Forms].[dbo].[cf_bp_main_instances].[status] driving that. I don't have any broken ones left, however if you sort by status in SSMS, I would think there is a numeric value that represents the status of "locked".  Any chance anyone from Laserfiche could confirm and identify the value so I could query to determine any broken instances in the future?

I just ran across some more instances today that had a status of locked. I took a screenshot that shows they have been locked since 1/9/2025 (last assigned date). It would be extremely helpful if there was a built-in report to find these or process to take care of them automatically.

What is the numeric value of the locked status in the database?

How do I run workload report on all instances filtering by locked status?

How do I get notified when a task enters locked status permanently?

If the user has already completed the task, rather than restarting it, how do we move the process forward?

Why do the processes show In Progress and the Tasks Status in the process just shows Assigned if it is actually locked?

Process Tab

Tasks Tab

Locked user task has status = 2 in db table [cf_bp_worker_instnc_to_resume].

"If the user has already completed the task, rather than restarting it, how do we move the process forward?" - can you please check there is any entry in db table [submission_recovery]?

We didn't intend to expose the locked status in Forms site as user tasks are not expected to be locked. It could happen if task was submitted when routing service was stopped, but once routing service was back, it should auto recover the submission and mark the user task completed.

So we would show locked user task as in progress/assigned. The one showing locked was likely not handled properly.

If you have encountered cases that user task would be locked even when routing service was operating normally, please let us know.

For us, this probably happened when we were restarting the Routing service, but the submissions did not auto recover as you said should happen. I ran the query on the [cf_bp_worker_instnc_to_resume] table, and I got back 24 rows, some of them dating back to 2024.

We do not have any entries in the [submission_recovery] table.

In this case, I am glad that you are showing the locked status or else we would never know that something wasn't working.

I have gone through all the ones I received back from the [cf_bp_worker_instnc_to_resume] table with a status of 2. 4 of them are on a Workflow Task step and 2 of them have instances that show as completed and so do all the steps. For the 2 that show completed, there are 2 terminated user tasks that were restarted. How do I correct these?

I found many rows by searching for status=2 in the database, however when I search the task or instance pages for worker_instance_id or last_submission_id I don't get any results.

I do not see a column which tells me the name of the process or the process ID the task is locked under.

There is a column which shows Due Date though so I could search for Due Status Overdue and reduce the results to under 3,000 and sort by status.

However when I sort by status it is surprisingly not sorting alphabetically so I can not group the locked tasks.

When you sort by a column, what is it sorting by that would put I before L and after? By sorting this way, the locked tasks are spread all over the report.

We are encountering cases with locked tasks when the routing service is operating normally but in our case only in this specific build 12.0.2503.10378. Both customers reporting this have the same build.