You are viewing limited content. For full access, please sign in.

Discussion

Discussion

Forms - Unlocking tasks in queue to be processed, viewing the queue

Forms
Updated October 19, 2020
posted on October 7, 2020

A few users had tasks that were locked on them after submitting, this is the message we receive when viewing the task status under Monitor.

This task has been locked because a submission has already occurred but hasn't been processed.

We waited 15 minutes and it was still showing this message.

Verified other tasks were going through executed after these tasks were submitted.

Checked the Forms events logs for any errors and it was clean.

Restarted the routing service responsible for processing these actions.

Eventually we had to re-assign the tasks which causes them to be started over, in order to unlock them.

Is there a better way to unlock these or view the queue so we can see what is wrong?

What is odd is that newer tasks were being processed before these tasks, so it wasn't that the routing service was behind, but that it was putting these in a holding pattern. A holding pattern I have no visibility into.

0 0
replied on October 15, 2020

The user task will be marked as locked after user submit the form before the submission is processed by Routing Service to avoid user fill out the form twice. The user task will be in locked status if 1)the submission is not processed yet or 2)there is some error to process the submission.

For situation 1), you should be able to find the submission XML under C:\ProgramData\Laserfiche Forms\RoutingError folder. The XML file contains information of CurrentStepId and ProcessId information which can be used to identify the submission is for which task.(you can use tool such as Sublime Text to open the RoutingError folder and search in the folder).

For situation 2) usually there will be error in event log but there maybe some unknown error that didn't get log.

If you open a support case with the RoutingError folder and the backup of Forms database, we can figure out whether the submission file exist in the folder.

1 0
replied on October 16, 2020

Ah, I didn't know about the C:\ProgramData location on the actual hard disk. Was looking around under the Monitor and in the Event Viewer, that is where I always go to find errors. Will add this 3rd location to my list.

We eventually found the errors on the SQL side and it was caused by large file uploads within the task that were too large for the database size restriction.

0 0
replied on October 19, 2020 • Show version history

So it was because the Forms database reach the size restriction(they use SQL Express?)and the user task submission is not processed successfully? What error did you get on SQL side?

0 0
replied on October 19, 2020

Yes, they use Express with the 10GB limit. They were trying to keep a 180 day file upload retention though, which was overkill. Just needed to dial it back so that their flow of file uploads stays within the range.

Just that they were trying to exceeding the maximum database size.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...