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

Question

Question

Force Entry Lock to terminate workflow

asked on February 8

We have a workflow that is suppose to move a document to a folder.  The users frequently leave this document open for editing when the workflow runs which causes the entry lock error.

 

The problem is that the rest of the workflow finishes past this point which does a whole lot of database activity and template updating and is cause problems and lots of time reprocessing things.

Is it as easy as checking the Critical Error box on that specific error task in the workflow admin console?    

Does the service need to be restarted for this to kick in once done (if this is the right way to do it)?

 

Thanks,

Chris

0 0

Replies

replied on February 12

One thing to keep in mind is that editing the task error handler will make the 9014 error fatal in all activities on this server.

I can't tell from the screenshots, but if the workflow moved on and executed activities following this "Route to Invoice Pending Payment", then the lock was released and this activity has successfully performed all its duties.  The messages pane should have one warning line for each time it tried and hit the lock.

1 0
replied on February 8

You could also use a Try-Catch activity. Then you'd be able to run specific activities after the error was caught. For example, you could send an email, or perform a cleanup operation.

0 0
replied on February 8

Try Catch never really catches as the activity simply waits to retry.  I'd almost like it to just terminate immediately.  

0 0
replied on February 8

Another option would be to add an SDK Script activity. The DocumentInfo has an IsLocked property that you can check. If you wanted to go further, there is also an EntryLock property that you can use to track down who exactly has the lock.

0 0
replied on February 8

Correct, but as to the original question, am correct in that if I check the box on that error handling menu it will interrupt the workflow?

0 0
replied on February 8 Show version history

It should. Although, as you pointed out, the Route Entry activity might pause things on it's own for a while before it bubbles it up to the Workflow to handle. It certainly won't make things worse to try it and see what happens.

@████████ or @████████ can probably be more specific about the way errors propagate.

0 0
replied on February 8

The I am using imbedded Forms in WebAccess for this so the workflow already contains a Find Entry activity for the routing.  Along the lines of the SDK lock check I guess I could add the additional property of Entry Lock Type in the Find Entry acticity.  Check if it is 0 or 1 and go from there.

0 0
replied on February 9 Show version history

Chris,

We have similar issues and I can confirm that checking that box caused our workflows to terminate rather than retrying and continuing regardless of the result.

Errors flagged as "critical" in the error handler settings will stop the workflow at the point of the error (or trigger a try-catch) and prevent the additional activities from running.

Try-catch doesn't seem to catch non-critical errors (warnings), which depending on your settings can come up with script activities as well.

The problem with checking the lock state is that the time between activities is brief, but it still leaves a small window in which that state could change.

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

Sign in to reply to this post.