Question

Entry Locked : 9045

Workflow

Updated December 9, 2021

asked on March 4, 2014

I have a workflow that is running to move documents to a new folder structure. However, during the process...my Workflow keeps encountering a Locked Object (error 4045). However, if I go into the Admin Console, there is no entry listed...and I have to restart the Laserfiche Service and then run the workflow again. Any ideas on what can be causing this?

0 0

Replies

replied on March 4, 2014

Any chance there is a entry with a security tag on it that is causing the problem?

1 0

replied on March 4, 2014

Workflow is trying to move the document but the document is locked by another action. It could be that you inadvertently have a second workflow acting on the same document on the same condition.

0 0

replied on November 22, 2017

Hi Matt ,

Is there any way to make make these workflows wait until other workflows finish work.something like "queuing"

0 0

replied on March 4, 2014

No security tags, and I only have one Workflow running. Here's my workflow...not doing anything complicated:

0 0

replied on March 4, 2014

Which activity is running into the warning? If you search in Workflow by the entry ID how many workflows are starting?

0 0

replied on March 4, 2014

Daryl, if the WF completes successfully (in other words if the warning is reported just once and the doc is moved), you can just ignore the message.

Somewhat unrelated, is there a reason why you read its fields before and after you set the fields on the doc?

0 0

replied on March 4, 2014

Miruna,

Yes (and I'm sure I probably didn't need to), but my logic was that the NEW ACCOUNT number doesn't exist in the field data until after the query, so I did the first Retrieve Field values to get my look criteria, then after the Query and the NEW ACCOUNT number is assigned, I did another Retrieve Field Values to use the NEW ACCOUNT number to create the new folder structure. Perhaps I didn't need to?

0 0

replied on March 4, 2014

That sounds fine. Though, if you get the new account number from SQL and write it to LF, you don't need to get it from LF again.

I'm just seeing a lot of that setup in workflows from support cases where the field values are not used for anything else after being read. And in that case, it just makes everything inefficient since we're making extra calls to LF for data that is not used and that we have to keep around in the WF DB until the workflow is complete. So I just wanted to make sure you're using the values.

0 0

replied on December 8, 2021

Hi All,

I am facing similar issue although with some difference. I have workflow which updates fields of a locked entry, can also see locked entry in the workflow admin console but was not able to release the lock with admin user as well.

Any ideas why it happened....

0 0

replied on December 9, 2021

"Entry locked" messages are not inherently a problem. In a reasonably busy repository, it is possible that other users or applications and Workflow, or multiple Workflow instances are attempting to access a document at the same time. That is why Workflow will retry its actions if it runs into a situation where another user has the document locked.

I'm not sure what you mean when you mentioned releasing locks through the workflow admin console. That's not functionality available in Workflow.

0 0

You are not allowed to follow up in this post.

Question

Question

Entry Locked : 9045

Replies

Sign in to reply to this post.